Skip to main content

Repairing a corrupt mssqlsystemresource database...


We know that mssqlsystemresource is another vital system database which is essential for normal operations of SQL Server. (Please refer to http://blog.consultdba.com/2010/03/note-on-resource-database.html for details). So if in an unlikely case if mssqlsystemresource gets corrupted, SQL Server will be unable to operate properly.

Unfortunately there is no direct way to repair mssqlsystemresource as it is not a standard database. However if you need to fix mssqlsystemresource, retrieve a copy of mssqlsystemresource.mdf and mssqlsystemresource.ndf which was backed up before the corruption and simply overwrite existing (corrupted) mssqlsystemresource.mdf and mssqlsystemresource.ndf with the (good) backed-up copies. This will immediately fix the issue. Please be advised that as mssqlsystemresource gets updated with SQL Server upgrade, it is highly recommended to backup mssqlsystemresource (mssqlsystemresource.mdf and mssqlsystemresource.ndf) before any upgrade procedure along with having a standard backup mechanism to regularly backup mssqlsystemresource.mdf and mssqlsystemresource.ndf with any other database as a part of DR solution.

In case if you do not have a backup of mssqlsystemresource, then you may copy mssqlsystemresource.mdf and mssqlsystemresource.ndf from another similar SQL Server and overwrite existing (corrupted) mssqlsystemresource.mdf and mssqlsystemresource.ndf with the (good) copies. (This SQL instance must be at the exactly same level (version number etc) with the corrupted instance). This will resolve the issue related to corrupted mssqlsystemresource. However if you need to execute this procedure, you must immediately arrange a regular backup mechanism of mssqlsystemresource database as a part of DR solution.
Labels:
Location: Greer, SC 29650, USA

Comments

Post a Comment

Popular posts from this blog

How to kill a negative SPID (like SPID -2) in SQL Server?

Rarely this scenario will arise when most likely you see this negative SPID (most likely SPID -2) is blocking other transaction causing issues. If you try to kill it using normal KILL command, it will fail reporting below error: Msg 6101, Level 16, State 1, Line 1 Process ID <SPID Number> is not a valid process ID. Choose a number between 1 and 2048 This is because of an orphaned distributed transaction ID.  Please follow below steps to kill it: Step 1: -- Find the UOW Number select req_transactionUOW from master..syslockinfo where req_spid = <SPID Number> --  <SPID Number>  is -2 most likely. Step 2: -- Copy the UOW number from Step one KILL ‘<UOW Number>’ This will kill the negative SPID resolving the issue.  However please note following points: 1. For SPID -2, you may find multiple UOW numbers. Please start killing them one by one. Typically killing first UOW will resolve the issues. (ie. will kill all UOW and release
Post a Comment
Read more

DMV/TSQL to find out basic hardware information of the SQL Server including when SQL Server started.

Please use below code: However, please be advised that it can not tell correct information around virtualization.  For example, it will show Hypervisor even if SQL runs on a physical OS where Hyper-V is on. So use this query only when you do not have sufficient access on underlying Windows Operating system to get these information directly. -- Basic hardware information for SQL Server (sys.dm_os_sys_info) /* This query is courtesy of https://sqlserverperformance.wordpress.com/. All credits goes to original author. */ SELECT cpu_count AS [Logical CPU Count] , scheduler_count , hyperthread_ratio AS [Hyperthread Ratio] , cpu_count / hyperthread_ratio AS [Physical CPU Count] , physical_memory_kb / 1024 AS [Physical Memory (MB)] , committed_kb / 1024 AS [Committed Memory (MB)] , committed_target_kb / 1024 AS [Committed Target Memory (MB)] , max_workers_count AS [Max Workers Count] , affinity_type_desc AS [Affinity Type] , sqlserver_start_time AS [
Post a Comment
Read more

‘Trace Skipped Records’ – What is this and how to resolve it while using SQL Server Profiles?

In some very rare case, you may experience a very weired message in profiler’s output as ‘Trace Skipped Records’ while you trace something on SQL Server. Screenshot of similer situation is as below: This is not an error but it comes by design of SQL Server (I believe so). When you are using SQL profiler and return data is too big to fit in the GUI (for me, it is an enormous xml), SQL Server simply prints this message and proceed to next step. Mostlikely this is to save server’s memory and performance. Although not suggested and guranteed, you can try to run a server side trace and dump data in a file which should capture all the data. However, it is strongly not recommended to run a trace on your production server from server side. Microsoft will probally document this limitation in future. More details may be found at https://connect.microsoft.com/SQLServer/feedback/details/304225/msft-edw-profiler-displays-trace-skipped-records-for-large-530kb-batch 
Post a Comment
Read more