Sometimes, the Microsoft SQL server can not be able to access one of its database and sets the corresponding bit as something other than normal in the status field of the ‘sysdatabases’ table. After this, the particular database appears as ‘SUSPECT’ in the Enterprise Manager of the SQL server. When any database is marked as ‘SUSPECT', you may encounter error messages while accessing the same. Moreover, the mounting of the database is halted with the error messages and the database becomes completely inaccessible. Under such situations, in order to bring back your important data from the troubled database, you need to use any utility which can repair SQL.
There can be some sort of corruption to the SQL database which has triggered SQL server to mark it as SUSPECT. In such case, the error message that you receive may be as below:
"96/11/18 10:48:32.60 kernel udopen: Operating System Error 32 (The
process cannot access the file because it is being used by another
process. ) during the creation/opening of physical device,
C:\DATA\SQL\MSDB. DAT (or C:\DATA\SQL\MSDB. MDF)
96/11/18 10:48:32.60 kernel udactivate (primary): failed to open
device C:\MSSQL\DATA\MSDB. DAT (or C:\DATA\SQL\MSDB. MDF) for vdn 127"
After the occurrence of the above error message, you will be unable to access the particular SQL database and the error pops up each time you try to access the database.
Apart from the database file corruption, it may be any missing device driver, renaming of the database, changing location of the database file, up-gradation of the operating system etc which can result in the inaccessibility of the database by the SQL server.
- Below steps may help you in resolving the problem and help you access the troubled SQL database once again:
- If it is the case of missing device driver file, ensure that the file is available.
- If it is the case of a sure database corruption, below steps will guide you through the resolution process:
- Drop all the indexes of the database and recreate them once again.
- After the above step, copy every record from the original database table and paste them into a newly created one.
- Update the statistics.
- Run the command ‘DBCC UPDATEUSAGE’.
- Lastly, run the command ‘sp_recompile’.
After performing all the above steps, if you are unable to resolve the issue and Enterprise Manager still shows the database as ‘SUSPECT', then try to restore the data from any previously taken valid backup. However, if backup is unavailable, then, you need to opt for any SQL repair utility to repair SQL database and retrieve the data back.
Stellar Phoenix SQL Recovery is an absolutely risk-free utility to perform mdf repair from SQL Server 2008, 2005, 2000 and recover backup all your database components back safely. Moreover, this MS SQL repair software is compatible with almost all Windows OS and is very much simple to be used by any user without much technical knowledge.