rebuild master database in sql server 2016 step by step

It will probably show 0x01 (sa) for one of the results, and an Active directory SID for the other one: Select From _principals Where Name = 'DBO' Select SID from master.sysdatabases Where Name = 'msdb' To find out what SID is where, run the following script.Wait for the instance to start, and log in using SSMS.Do not mess with those, just add a new one using the handy “Add” button provided. There will be some existing startup parameters. You can do this by command line if you wish, but for clustered instances it is easier to use SQL Server config manager. Start the instance with trace flag 902 to disable the upgrade scripts and get the server back online.To be more specific, the master database does not like the looks of the owner attribute on the msdb database, and is down right refusing to complete the upgrade process. Something went down the steep road to oblivion during the upgrade process, and the instance is as dead as an overrun squirrel. For more information about how to rebuild the master database, see SQL Server Books Online. Restore master from a full backup, repair it, or rebuild it. 14:32:23.39 spid14s Cannot recover the master database. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. This is a serious error condition which might interfere with regular operation and the database will be taken offline.

14:32:23.39 spid14s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 33009, state 2, severity 16. You should correct this situation by resetting the owner of database 'msdb' using the ALTER AUTHORIZATION statement. 14:32:23.39 spid14s The database owner SID recorded in the master database differs from the database owner SID recorded in database 'msdb'. After an upgrade to SQL 2012 SP3, a clustered instance fails to start listing error 33009, 9: 14:32:23.39 spid14s Error: 33009, Severity: 16, State: 2.

Rebuild master database in sql server 2016 step by step