If SSMS doesn't 'see' any specific database selected, it will use last server and default database (master most of the time) as a database for that query connection (Fig #2).Īlthough this is rarely done, this behavior could be changed by either hard-coding the database name via SSMS connection properties (Fig #3) or by changing the default database per login by running ALTER LOGIN WITH DEFAULT_DATABASE =. When SSMS user clicks on a New query button, SSMS makes the connection using highlighted/selected server and database (Fig #1). The main problem is SSMS' default behavior (to be exact, this is not purely SSMS behavior, but more of a SQL Server login default database setting). This article is going to discuss why user objects end up created in a master database and how to prevent this from happening.

It's highly recommended not to use it to store any user database objects.

SQL Server can't run without access to a fully functional master database. Just in case that you are not familiar with this database, the Master database is used in SQL Server to store all the system information, instance-level settings, logon information, database file locations, etc.

Use of master database in sql server