February 15, 2013 at 8:36 am
I have a question, a silly question, and I am prepared for the are you kidding me comments but alas I need opinions before I take my case to the folks that matter in my world.
The default database in login properties is set to master by default, fact.
Let's say I have a sql user, that accesses several different databases, but the default databases is pointing to DB3 not master, why would you not leave the default at master and change it to another DB?
This has been a debate for me, I always leave default at master, why would you not? I have research, read in books, and came up empty handed; but have not asked the question on here yet, so give it to me guys and gals...
MCSE SQL Server 2012\2014\2016
February 15, 2013 at 9:42 am
For one, convenience. I change my default DB sometimes so that when I connect I am dropped into the DB I use most often. When I setup new developers with a login I will set the default to tempdb so if they connect and run something but forget to change their DB context we do not end up with objects in master (yes, some developers are in the sysadmin Role in development).
For production systems it depends on the application or person. Some apps (thinking mostly third party here) do not have the ability to configure the the DB context to use, i.e. they rely on the server to drop them into the correct DB. And for some people it is just easier to set their default database to the database they'll be using rather than have conversations with them about USE or how to change their default DB.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply