InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 18:28:48 GMT20http://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxCorruption most likely, meaning something wrong with the IO subsystem. Can't say more without more info.btw, checkDB is the last resort for fixing suspect databases, you should rather have restored a good backupSat, 02 Mar 2013 13:48:24 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxHey Guys before few days my data source dropped into suppose method.I set data source using dbcc check db in urgent method and now it seems ok. But I don't know why this incident happens. does anybody know possible reason?Sat, 02 Mar 2013 12:15:27 GMTsaifulislam6720http://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxHello Gail, you are right... I completely forgot about that. :(... I remember that I had to put it on Emergency Mode in order to recover data, because, we did not have a backup that help us to recover our data... we did not lost data, but I lost a lot of time due to our past backup process.Fri, 30 Nov 2012 07:42:18 GMTSinfonico25http://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxHighly unlikely to work. SQL can only recreate the log file if the DB was cleanly shut down prior to the log being damaged/lost.Fri, 30 Nov 2012 00:09:52 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxIf only the Log File is corrupt you could try to attach only the Data File with:[code="sql"]sp_attach_single_file_db [@dbname=] 'dbname', [@physname=]'physical_name'[/code]Example:[code="sql"]sp_attach_single_file_db @dbname='DataBaseName', @physname='C:\SQLServer\Data\DataBaseName_Data.mdf'[/code]Edit :w00t::you must Stop the Production SQL Server Instance in order to copy the mdf file to another location and attach to a Test SQL Server Instance.Hope it help youThu, 29 Nov 2012 14:18:46 GMTSinfonico25http://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxI would suggest you to try third party utility such as recoveryfix for sql database repair software. This company providing a free trial version of software. You can get this software by performing search on Google.ThanksSun, 25 Nov 2012 23:29:20 GMTjonmichel72http://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxThanks GailWed, 14 Nov 2012 03:01:54 GMTRatheesh.K.Nairhttp://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxRestore from backup.IO problems, like most causes of corruption, or someone tried something stupid like replacing the data or log files with older ones, or maybe a HA/DR 'solution' like SAN snapshots that doesn't support SQL and hence is more a gamble than a solutionThu, 08 Nov 2012 09:18:21 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxWhat can be the cause for this?Thu, 08 Nov 2012 09:12:23 GMTRatheesh.K.Nairhttp://www.sqlservercentral.com/Forums/Topic1382538-2893-1.aspxHi Experts,Getting below error when tried to recover db from suspect mode..dbcc checkdb didnt give any error but when tried to make it online give thisThe log scan number (256603:182:1) passed to log scan in database 'PRD_dis 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.Msg 3414, Level 21, State 1, Line 1An error occurred during recovery, preventing the database 'PRD_d(database ID 6) 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.Thu, 08 Nov 2012 08:48:22 GMTRatheesh.K.Nair