Possibility 1 : Someone deleted or misplaced a log/data file when SQL server was offline so the database could not start as it is missing a file.
Solution : Put the missing file back on the location. SQL error log will give the exact location of the missing file.
Possibility 2 : SQL server could not access to put an exclusive lock on the data/log file while the database was starting up . This could be caused when the data SQL server is shared with some other tool ( e.g. antivirus)
Solution: Find the file handler that placed an exclusive lock on the data/log file and kill it. Then run the following query.
RESTORE DATABASE WITH RECOVERY
Possibility 3 : Due to a corrupted transaction. This could likely be that the SQL server went down in the middle of the transaction and while coming back it could not complete ( COMMIT/ROLLBACK) the transaction.
Solution: Switch to emergency mode and run the dbcc checkdb command
Possibility 4: Some OS/hardware failure
No comments:
Post a Comment