Resource Database Corruption:
What is resource database:
Resource database is a binary and a system database, and its corruption would not allow instance to start. If resource database is corrupt it is going to affect instance functionality.
Resource Database corruption:
If resource database gets corrupted, it’s more of a binary corruption. Hence a copy can be initiated preferably from same build, if not from a different build.
- If resource is corrupt, try to start instance with /t3608 and /m to confirm if at least instance starts with Master only mode.
- Review the event viewer. Ideally if resource corruption identified, copy the files from collocated instances.
Resolve issue:
Verify if RDB is corrupt or not, in Event viewer and SQL Server Error Logs.
If a valid database backup exists.
RDB backups are more of OS level file copy backups.
As instance isn’t starting, if backup is available copy and paste the Resource database files into BINN directory from the backup.
(C:\Program Files\Microsoft SQL Server\MSSQL15.DISTRIBUTOR\MSSQL\Binn).
Start the instance.
If RDB backup is not available:
We have to do REPAIR installation of SQL Server.
REPAIR will perform entire repair of instance and also Master, Model, MSDB and TEMPDB are rebuilt.
Approach1:
Run–>Appwiz.cpl–> SQL Server 2012 (64Bit) –>Right Click –> Uninstall/Change –> Repair –> It would ask to map to Media directory –>Perform Repair installation.
Approach2:
Open Setup.exe from Media -> Maintenance -> Repair.
Using both approaches are similar, and it would perform rebuild of resource and system databases.
After rebuilding Resource database, restore Master, Model and MSDB backups (if backup are available).
Approach 3:
Alternate option is to COPY RDB files from another instance and overwrite existing RDB files in the instance. This should meet one criterion i.e. the files being copied should belong to SAME VERSION and BUILD.
Note: If resource database is corrupted, rebuilding master will rebuild the resource database.
