|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 10:43 PM
Points: 407,
Visits: 73
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Friday, March 01, 2013 10:30 AM
Points: 366,
Visits: 337
|
|
Not sure what you are referring to in step 2: --2. Stop MSSQLSERVER service, replace created mdf file with original one
Nancy
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 8:14 AM
Points: 1,081,
Visits: 1,457
|
|
this appears to be for SQL 2000 or below. You cannot update system tables in SQL 2005 or above.
The best article on this subject is from Gail Shaw - http://www.sqlservercentral.com/articles/65804/ for SQL 2005 and above.
Tim White
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Friday, March 01, 2013 10:30 AM
Points: 366,
Visits: 337
|
|
Thanks, didn't catch the SQL 2000 part.
Nancy
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, March 09, 2011 8:33 AM
Points: 216,
Visits: 43
|
|
When ever you find that the data base is in suspect mode use the below script.
Exec Sp_resetstatus ‘Yourdbname’
Alter database yourdbname set emergency
Dbcc checkdb(yourdbname)
Alter database yourdbname set single_user with rollback immediate
Dbcc checkdb (‘yourdbname ‘, repair _allow_data_loss)
ALTER DATABASE yourDBname SET MULTI_USER
Regards, Adapala.N
|
|
|
|