Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Database Naming Convention Expand / Collapse
Author
Message
Posted Thursday, August 1, 2013 11:19 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 8:51 AM
Points: 815, Visits: 2,028
How many times have you had to provide an answer, verbal or written, as to what these arbitrary and meaningless prefixes mean? Add up that time, and then multiply that by your salary. These poor practices cost an awful lot of money.


They are obviously not arbitrary or meaningless. If I had said klw for my OLAP and xdr for my staging areas, that would be arbitrary and meaningless. Far enough point on the sa also being system administrator, but lots of abbreviations have multiple meanings.

I've never had to explain them beyond the explanation I gave above. So I would say, all in all, it's very little money. In any case, I'm not trying to convince anyone to change their names to what I think they should be. I'm personally just glad to know that people have naming conventions and use them. I've worked in both environments, and an environment lacking such conventions is harder.



Post #1480048
Posted Thursday, August 1, 2013 11:51 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 4:14 PM
Points: 15,725, Visits: 28,130
RonKyle (8/1/2013)
saFinance is shorter than FinanceStaging and dwKyle is much shorter than KyleDataWarehouse. The users don't see these names, so they don't have to be user friendly. I can see that some might prefer databases be grouped, in which case the suffix would be better, but I like to have my staging areas grouped together, so I need the prefix.

Some would say I'm giving away my Microsoft Access roots, but no apologies for that.


Like I said, if it's working for you, great!


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1480061
Posted Friday, August 2, 2013 8:24 AM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 11, 2014 9:35 AM
Points: 9, Visits: 144
Thanks to everyone for all their replies. From all the comments I've read from everyone it looks, at least to me, that short database names are not favored by most.

As a post script to my original question, does anyone know of a definitive authority or publication that can nail this issue down and support the above short name conclusion I've reached?

Thanks!
Post #1480426
Posted Friday, August 2, 2013 8:59 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 4:14 PM
Points: 15,725, Visits: 28,130
From a purely technical point of view, short names don't hurt. They don't help either. A shorter DB name won't make backups run faster, queries run faster or decrease the load on your CPU or network.

So, from there, it becomes strictly a question of opinion. Does it make more sense to make typing a connection string (which usually isn't typed very often, at all) easier or should you go for clarity. I think most people here, and elsewhere, will fall on the side of clarity. But it's just an opinion.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1480449
Posted Friday, August 2, 2013 9:01 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 8:51 AM
Points: 815, Visits: 2,028
I think most people here, and elsewhere, will fall on the side of clarity. But it's just a opinion.


However, as you can see, it's an opinion held by many people with years of experience doing this. That's as close to authoritative as you will get on this subject.
//added word "many" to preceeding sentence



Post #1480452
Posted Friday, August 2, 2013 11:02 AM


Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 11, 2014 9:35 AM
Points: 9, Visits: 144
Thanks! I am pretty sure you're right.
Post #1480530
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse