Post reply

Visio and SQL Server naming conventions

  • September 19, 2003 at 2:20 pm

    #160149

    Is there any way to customize SQL Server to use tablename_PK, tablename_AK and tablename_IDX for primary keys, alternate keys

    and indexes? Since this is how Visio modeling tool does, and we would like to have a consistent naming conventions. We use visio

    for initial modeling and later some of the changes happen directly on the SQL Server. We do not want to see objects following conventions.

    Sometimes within the same table we have one index named one way and the other the other way.

    thanks.

  • September 19, 2003 at 2:32 pm

    #475123

    Not that I know of. I wish there was as a default.

    What I've done in the past is search for new objects each day and get them corrected ASAP.

    Steve Jones

    sjones@sqlservercentral.com

    http://www.sqlservercentral.com/columnists/sjones

    The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/

    http://www.dkranch.net

  • September 21, 2003 at 8:31 pm

    #475190

    The only way to apply this sort of standard is to always create objects using the same tool. So as you use Visio to create the objects, don't create objects using anything else. In reality, this can become a real pain. It'd be much easier to change the name around in Visio prior to saving/creating the object.

    Personally, I prefer having a prefix rather than a suffix. It also seems that more tools use prefixes than suffixes.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    --------------------
    Colt 45 - the original point and click interface

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply