October 26, 2010 at 3:56 pm
Well good ole SHarePoint (2010) is at it again, adding as much grief to the life of a DBA as possible. Thanks to SharePOint our IT Admins have setup a batch of new DB's that have spaces (thats plural meaning mroe then one space in a database name) in their name. Even though its valid to use a space we all know the headaches that this introduces. Can anyone help me out with some good Microsoft provided links/docs on why its not a good idea to use spaces in your object names in SQL Server so I can present this to my IT admins?
Thanks
Kindest Regards,
Just say No to Facebook!October 26, 2010 at 4:03 pm
The is probably nothing that can't be done by adding brackets around the name: [db name]
However, it is likely the many utilities may not work very well with this type of name, and I wouldn't count on Sharepoint being free from problems related to this. The point being that when you do run into problems, it may be a real problem to get past them, and you really have no way of knowing in advance if you will, so why look for trouble?
October 26, 2010 at 4:11 pm
I'm trying to provide additional material/refereneces to the IT guys about why this is a bad idea because when something does not work right because of this it will be on me to adress it. If that shoudl happen and I have provioded references to why this was a bad idea way back when it will greatly soften the blow on me to deal with it as I will be able to point back and say I warned you.
Its not about passing blame but about being able to proive that you did and in very clear terms try to warn others why this could come back to haunt us later. If I say nothing and 6 months or later something happens itr will eb easy to say "Why didn't you tell us something like this could happen".
Kindest Regards,
Just say No to Facebook!October 26, 2010 at 4:57 pm
One note at the bottom, and this is referenced from other places : http://vyaskn.tripod.com/object_naming.htm
http://belham.com/sql-server/naming-convention-for-your-sql-server-database/
Not a lot I see out there. I think MS encourages "easy names" for users.
http://corypeters.net/2009/06/admin-and-end-user-naming-conventions/
October 26, 2010 at 7:31 pm
On a side note - since you are on SQL Server 2008 you can implement a policy that prevents database names from having spaces - or any other special characters that will cause problems.
Probably won't make you IT Admins happy when it prevents them from creating the databases, but at least they'll be calling you before the database gets created and you can explain why it's such a bad idea.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply