![]() ![]() When should you restore or rebuild the master database? Read about the restrictions for master database in the restrictions section of the documentation. See the images below to see that while we can change the recovery model, it does not help us. On top of that, you can put master in Full recovery model, but you will not be able to create log backups for it. You can create and use tables etc., just like in any user database, but keep in mind this database has a special role when it comes to SQL Server. …”Īlso read the recommendations in that document. This includes instance-wide metadata such as logon accounts, endpoints, linked servers, and system configuration settings. The Microsoft Docs state: “ The master database records all the system-level information for a SQL Server system. The master databaseįirst of all, I want to remind you to not implement any critical objects in the master database, as it is a systems database for SQL Server itself. By cheer luck, the glitch vanished in time and the instance picked up its workings, so we double checked it all and didn’t need the actual recoveries to be performed. We reached out for the appropriate scenarios to recover the instance. Most articles cover restoring a master database on a local instance, if you’re lucky for a named instance, but most do not cover a clustered instance.Īs with everything in SQL Server, things evolve over time and versions! So, with every new version you prepare for, you also need to re-evaluate the scenarios you already tested for your current SQL Server instances.Īs we recently experienced a production instance that lost the ability to reach its SAN hosted database files, due to a glitch of the SAN backup mechanism. It doesn’t happen often you have to recover systems databases in SQL Server. ![]()
0 Comments
Leave a Reply. |