If severe damage to master prevents you from starting SQL Server, you must rebuild master. For more information, see Restore the master Database (Transact-SQL). If you can start the server instance, you should be able to restore master from a full database backup. Restore master from a current database backup. If master becomes unusable, you can return the database to a usable state in either of the following ways: If you do, master must be backed up more frequently.ĭo not set the TRUSTWORTHY option to ON for the master database. Changing server or database configuration valuesĭo not create user objects in master.Creating, modifying, or dropping any database.When you work with the master database, consider the following recommendations:Īlways have a current backup of the master database available.īack up the master database as soon as possible after the following operations: Setting the database or primary filegroup to READ_ONLY.Renaming the database or primary filegroup.Removing the primary filegroup, primary data file, or log file.Dropping the guest user from the database.

Creating triggers on system tables in the database.Creating a full-text catalog or full-text index.The default collation is the server collation. Backups, only a full database backup can be performed on the master database.The following operations cannot be performed on the master database: Database optionįor a description of these database options, see ALTER DATABASE (Transact-SQL). For Azure SQL Database single databases and elastic pools, the user has no control over these database options.

Rebuild master database sql server 2016