Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kunwar.naresh
Starting Member
1 Post |
 Posted - 2012-07-19 : 11:44:23
|
| Please suggest some for below said prob. Warning: You must recover this database prior to access.Msg 0, Level 11, State 0, Line 0A severe error occurred on the current command. The results, if any, should be discarded.Msg 5028, Level 16, State 4, Line 1The system could not activate enough of the database to rebuild the log.DBCC results for 'FY20102012'.CHECKDB found 0 allocation errors and 0 consistency errors in database 'FY20102012'.Msg 926, Level 14, State 1, Line 1Database 'FY20102012' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.Msg 926, Level 14, State 1, Line 1Database 'FY20102012' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.Msg 5069, Level 16, State 1, Line 1ALTER DATABASE statement failed.Msg 926, Level 14, State 1, Line 1Database 'FY20102012' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.Msg 5069, Level 16, State 1, Line 1ALTER DATABASE statement failed.Msg 824, Level 24, State 2, Line 1SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 3:31185152; actual 63104:235288040). It occurred during a read of page (3:31185152) in database ID 7 at offset 0x00003b7b200000 in file 'G:\MSSQL10.MSSQLSERVER\MSSQL\DATA\Lilliput Kidswear India HO_1.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Msg 3414, Level 21, State 1, Line 1An error occurred during recovery, preventing the database 'FY20102012' (database ID 7) 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. |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2012-07-19 : 12:04:10
|
| You have a storage error. A page isn't where the database engine expects it to be.Seems like a time to put your backup/recovery plan into action.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
prett
Posting Yak Master
212 Posts |
Posted - 2012-07-23 : 02:45:10
|
| If you have good backup copy then restore your database from backup otherwise use emergency mode repair to fix up this issue. Check this post: http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/18/636105.aspx If it does not work then there is only way to fix up the database is to use SQL repair software: http://lmgtfy.com/?q=sql+repair+software |
|
|
|
lincoln
Starting Member
1 Post |
Posted - 2014-04-14 : 05:45:32
|
| The T-SQL script command DBCC CHECKDB job is identify the level of consistency related to pages, index and tables of the SQL database during his checks if he finds some kind of error the command immediately reports an error. You can try SQL database recovery software from here :- unspammed |
|
|
|
pladrounf
Starting Member
3 Posts |
Posted - 2014-08-23 : 08:28:23
|
| In such critical scenario of disaster the use of Recovery Toolbox for SQL Server is relevant and secure option. Get it from here www.sql.recoverytoolbox.com/[url][/url] |
|
|
|
|
|
|
|
|
sal 1/0 error recovery error