Hi,
I am trying to restore SQL2K DB backup to SQL2005 Express. The process goes fine, but at the end of the process (100% progress), it shows error Restore Could not start database.
It does not provide more detail to remedy the error.
Anybody faced this problem and have any solution?
Thanks,
Hiten
What happens when you manually start the sql server services?|||SQL server services are running, but the database is not online. It puts the database in to suspect state.
I looked in to event logs, and it turned out that the database I was restoring already had 'sys' sql user , since in 2005 sys user is reserved, the restore operation tried to rename it to something else, the log shows following message
Warning: User "sys" (principal_id = 24) in database "Test" has been renamed to "_ID_0x00000018_RENAMED_FROM_sys". "sys" is a reserved user or schema name in this version of SQL Server.
There were few other error/warnings for objects used by sys.
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_CurrentStatusID_7080FE81" (index_id = 2) on object ID 1887501953 in database "Test". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_NextStatusID_7080FE81" (index_id = 3) on object ID 1887501953 in database "Test". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_TransitionString_7080FE81" (index_id = 4) on object ID 1887501953 in database "Test". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
and at last
Warning: Database "Test" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.
RESTORE could not start database 'Test'.
The database 'Test' is marked RESTORING and is in a state that does not allow recovery to be run.
In the end, it puts database to suspect. I don't know how to bring it back to online for multiple users. When I tried to bring it online using ALTER DATABASE command, it brought it online for single user only, which did not serve my purpose, and I don't know what needs to be cleaned up to this database.
I hope this will give u some idea of what happened.
I would appreciate any suggestion..
Thanks,
Hiten
No comments:
Post a Comment