InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 15:21:26 GMT20http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspx[p]Server reboot is not an easy job as it looks like. You should be very cautious while rebooting your SQL server because any minor mistake can corrupt your whole SQL database, i think the same happened with you and you had a list of corrupted and suspected files which you tried to fix with some coding but the problem is not resolved because these coding don't provide a proper solution. You need to have a commercial tool that can fix the errors of your corrupted SQL database.[/p][p]You can get more information about the management tool from [url=http://www.mssqlrepair.n.nu/repair-corrupt-ms-sql-database.html]http://www.mssqlrepair.n.nu/repair-corrupt-ms-sql-database.html[/url], it will help you to repair the corrupted files.[/p][p]And one more thing I would like suggest you that please don't reboot your MS SQL Server incautiously next time.[/p]Sat, 14 Apr 2012 05:01:16 GMTstephencook2913http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxAnd sometimes the sign posts get lost..... all we can do is but try ... :-PThu, 04 Mar 2010 18:06:48 GMTMalcolm Daughtreehttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspx[quote][b]TheSQLGuru (3/4/2010)[/b][hr][quote]Sometimes just reading forums regularly helps to gain knowledge ![/quote]Actually you didn't need to read this forum to gain knowledge. That stuff you watched has been on the web for a long time now. :-D[/quote]I agree .. but sometimes the obvious remains obscure ! :-)\\KThu, 04 Mar 2010 18:02:17 GMTSQLQuest29http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspx[quote]Sometimes just reading forums regularly helps to gain knowledge ![/quote]Actually you didn't need to read this forum to gain knowledge. That stuff you watched has been on the web for a long time now. :-DThu, 04 Mar 2010 13:32:52 GMTTheSQLGuruhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspx[quote][b]Malcolm Daughtree (3/3/2010)[/b][hr]Hey Paul, If you won't beat your own drum I willGO HERE !!!!http://www.microsoft.com/emea/teched2008/itpro/tv/default.aspx?vid=78. LEARN Enjoy! I did and have discovered the Power of DBCC page and Checkdb, and directly aided me recovering a large Database faster than a 4 hour restore.Also I'd suggest you hunt up a copy of Rodney Landrum's eBook "SQL Server Tacklebox" especially the last chapter.CodeOn:-P [/quote]Thanks Malcolm for pointing to a wonderful webcast of Paul explaining details of corruption with practical demos. I saw the whole and learned a lot. :-)Sometimes just reading forums regularly helps to gain knowledge !\\KThu, 04 Mar 2010 12:48:28 GMTSQLQuest29http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxHey Paul, If you won't beat your own drum I willGO HERE !!!!http://www.microsoft.com/emea/teched2008/itpro/tv/default.aspx?vid=78. LEARN Enjoy! I did and have discovered the Power of DBCC page and Checkdb, and directly aided me recovering a large Database faster than a 4 hour restore.Also I'd suggest you hunt up a copy of Rodney Landrum's eBook "SQL Server Tacklebox" especially the last chapter.CodeOn:-P Wed, 03 Mar 2010 16:34:24 GMTMalcolm Daughtreehttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxThanks Paul.I had read about deleting the log file on another site. I just didn't have the guts to try it. Maybe I will give it a whirl. At this point I have nothing to lose.ThanksQuinnFri, 27 Jun 2008 13:26:20 GMTQuinn-793124http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxPSS won't be able to do anything different.One of the steps of emergency mode repair is to try forcing recovery with the equivalent of WITH CONTINUE_AFTER_ERROR - looks like in this case it's caused the recovery code to hang. This is only the second time I've seen it fail since I wrote it - but it's a last ditch effort when everything's corrupt and there's no backup so I'm not surprised there are some cases where even it can't 'fix' things.Your only options at this point are: 1 EMERGENCY mode and extract into a new database 2 delete the log file and run repair#2 should only be attempted if you're comfortable. It's really ok as the log and database are corrupt anyway, so you're not losing anything by manually throwing away the transaction log. Follow these steps: - shutdown - make a complete copy of all database files on separate storage (in case you want to go back to your current state) - delete the log file from the database - start up - put the database in emergency mode - run repair - this won't try to run recovery this time, but will simply create a new log file and then run a full repairYour data will be transactionally inconsistent and you'll have lost some but the database will be usable by SQL Server (not necessarily your application).Do all of this at your own risk. The most important thing is to make a copy of all the database files before you start so you can go back to your current state.ThanksFri, 27 Jun 2008 12:50:44 GMTPaul Randalhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxPersonally I think this is a time to call Microsoft Product Support.Fri, 27 Jun 2008 07:32:05 GMTTheSQLGuruhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxExcellent.If you find there is data you can't recreate, post again here and I'll try and help you salvage as much as possible from the DB.You may also want to do some checks on the hardware on that server, specifically on the storage system, to see if you can find a cause for the corruption.Thu, 26 Jun 2008 01:03:07 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxGail,I appreciate all of your help. I think I am going to call it a loss. THe DB is a holding area for as400 data for use with our GIS system and I think it can be recreated after I talk to the as400 people.Thanks AgainQuinnWed, 25 Jun 2008 12:37:23 GMTQuinn-793124http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxI'm not sure how to recover from that problem without loosing some data. If you try to set the database into emergency mode, can you view the tables? Can you select data from them? Don't try running repair. It won't help in this scenario.How big is the database?Wed, 25 Jun 2008 11:35:17 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxNone at all Gail.QuinnWed, 25 Jun 2008 08:29:22 GMTQuinn-793124http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxDo you have replication on either of these databases?Is there any chance that someone has been messing with the files?Very important, do you have a backup?Tue, 24 Jun 2008 23:53:23 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxGailWe found out yesterday that the backup of both the sql and sql express DB's had not been working. We are not exactly sure why.There isn't anything in either log files that stands out as making it go into recovery mode. Here is the part where it finds a problem starting up the DB.2008-06-23 08:29:13.21 spid55 Starting up database 'KoochData'.2008-06-23 08:29:13.21 spid55 Error: 9003, Severity: 20, State: 1.2008-06-23 08:29:13.21 spid55 The log scan number (145:4893:239) passed to log scan in database 'KoochData' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. 2008-06-23 08:29:13.21 spid55 Error: 3414, Severity: 21, State: 1.2008-06-23 08:29:13.21 spid55 An error occurred during recovery, preventing the database 'KoochData' (database ID 8) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.Before that was a bunch of messages that show the state of the DB. Like emergency mode, single user mode, and multi user mode. That was from me exucuting the code from the first thread.I wanted to get it out of suspect mode and read online the way to do that was to change to emergency mode. I was trying to get to a point where I could run dbcc.Do you know of any good recovery software?ThanksQuinnTue, 24 Jun 2008 12:37:03 GMTQuinn-793124http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxDo you have a backup?Can you look at the error log and see if there's any entry there that indicates why the database is in recovery-pending?Tue, 24 Jun 2008 11:53:26 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxAlsoWhen I right click on the DB and go to properties I get the same 922 message however it says it is in recovery mode. When I look at sys.databases I see the state is 3 and state_desc is recovery pending. Do these have to be changed to be able to do DBCC?Thanks againQuinnTue, 24 Jun 2008 09:39:26 GMTQuinn-793124http://www.sqlservercentral.com/Forums/Topic522582-266-1.aspxWe had a server reboot the other night and it seams to have corrupted several files. I have a database in SQL Express that is corrupt and one in regular SQL that was labeled suspect. I found this on a web site for fixing suspect DB's. ALTER DATABASE koochdata SET EMERGENCYDBCC checkdb('koochdata')ALTER DATABASE koochdata SET SINGLE_USER WITH ROLLBACK IMMEDIATEDBCC CheckDB ('koochdata', REPAIR_ALLOW_DATA_LOSS)ALTER DATABASE koochdata SET MULTI_USERWhen I issue these one at a time I can see in the log files that the DB is changing status but when I run the dbcc commands I get this result.Msg 922, Level 14, State 1, Line 1Database 'KoochData' is being recovered. Waiting until recovery is finished.Query completed with errorsI haven't been able to find msg 922 anywhere. Is there a reason that dbcc doesn't want to work? It didn't leave a message in the log file just the changes in the DB status.Also. Can I use the same procedure in Sqlserver express?Thank you in advance.Quinn McCarthyTue, 24 Jun 2008 08:25:14 GMTQuinn-793124