none
Is it a bad idea to create a schema named [com] and if so why? RRS feed

  • Question

  • Is it a bad idea to create a schema named [com] and if so why.  I am creating a schema for our communications dept and [com] works unless there's a risk I don't know about.
    Tuesday, June 30, 2020 8:14 PM

Answers

  • I don't see a problem with that name although probably communication may be a better name (but longer to type).

    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog


    My TechNet articles



    Tuesday, June 30, 2020 8:19 PM
    Moderator
  • Hi iTrackData,

    Usually you need to note that whether the schema name is easily understood( clear and simple), no plural, and no prefix or suffix.

    Naming the schema as [com] is allowed. But the [com] as a very general abbreviation, I think it might be better to use [comm] instead.

    Best Regards,
    Cris


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, July 1, 2020 3:17 AM
  • By old SQL guys (like me) schema's are not very beloved, because in old days (up to SQL Server 2000) schemas was bound to a database user; if you wanted to drop the user you have to drop the schema as well and this meaned to change all queries.

    Since 2005 schemas are "standalone" objects and are very useful to organize objects and control permissions. And the name don't matter, als long as you don't use reserved key words.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:00 PM
    Wednesday, July 1, 2020 5:26 AM
    Moderator
  • Naomi N,  Thank you for your feedback!  Very helpful.
    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:04 PM
  • Hello Cris Zhan, 

    Thank you for the suggestion.  I see your point and it's well taken.

    Kind Regards

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:06 PM
  • Hello Olaf Helper,

    I appreciate your assistance and link to the reserved key words.  Very helpful.   Thank you!! 

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:09 PM

All replies

  • I don't see a problem with that name although probably communication may be a better name (but longer to type).

    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog


    My TechNet articles



    Tuesday, June 30, 2020 8:19 PM
    Moderator
  • Hi iTrackData,

    Usually you need to note that whether the schema name is easily understood( clear and simple), no plural, and no prefix or suffix.

    Naming the schema as [com] is allowed. But the [com] as a very general abbreviation, I think it might be better to use [comm] instead.

    Best Regards,
    Cris


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, July 1, 2020 3:17 AM
  • By old SQL guys (like me) schema's are not very beloved, because in old days (up to SQL Server 2000) schemas was bound to a database user; if you wanted to drop the user you have to drop the schema as well and this meaned to change all queries.

    Since 2005 schemas are "standalone" objects and are very useful to organize objects and control permissions. And the name don't matter, als long as you don't use reserved key words.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:00 PM
    Wednesday, July 1, 2020 5:26 AM
    Moderator
  • Naomi N,  Thank you for your feedback!  Very helpful.
    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:04 PM
  • Hello Cris Zhan, 

    Thank you for the suggestion.  I see your point and it's well taken.

    Kind Regards

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:06 PM
  • Hello Olaf Helper,

    I appreciate your assistance and link to the reserved key words.  Very helpful.   Thank you!! 

    • Marked as answer by iTrackData Wednesday, July 8, 2020 8:01 PM
    Wednesday, July 1, 2020 7:09 PM
  • Hi friend,

    Thank you for your reply. In order to close this thread, please kindly mark useful replies as answers. By doing so, it will benefit all community members who are having this similar issue.  Your contribution is highly appreciated.

    Best Regards,
    Cris


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 6, 2020 1:31 AM
  • Hi Chris, 

    I marked more than one as "answer" because they all were helpful.  I don't protocol, I am totally new to asking questions in forums.  Please let me know if I need to adjust.


    Wednesday, July 8, 2020 8:04 PM
  • Hi friend,

    Have a nice day! Thanks for your post and reply.

    If someone answers your question please mark their reply as the answer to your question. You can also mark multiple replies as answers if you think they answered your question.  Marking replies not only assists others with similar questions, it also let's people know that you're grateful for their assistance.
    ---One of the community guidelines


    In addition, if you have another question, please feel free to ask.

    Thanks for your contribution again.

    Best Regards,
    Cris


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, July 9, 2020 1:14 AM