Grant Fritchey (8/1/2013)
Clarity, clarity, clarity.You need to make things clear. Keeping the names arbitrarily short does nothing but obscure meaning. You want to know what things are, quick, clear and simple. In fact, this should be your naming standard for everything. Keep things clear.
I agree. You want to be able to know what the database (or object) represents quickly and not have to look it up in some documentation translator.
I'm also completely against naming databases based on the environment they are in. That makes things EXTREMELY difficult to manage for testing, coding, rollbacks from production, etc.
<sarcasm> I love the databases suffixed with _DEV that end up being the production database. </sarcasm> That takes a bit of getting used to.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events