Crashed db recovery

Hello,

i've got MS Windows Server 2003 OS (RAID 10) and MS SQL 2005, however server crashed with "blue death" screen. After forced reset, SQL server marked my db as a SUSPECT. Tried DBCC CHECKDB with no luck, what can i do to bring it back to life, please? (have no backup).

Msg 926, Level 14, State 1, Line 1
Database 'IRIX' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:182; actual 32:7602287). It occurred during a read of page (1:182) in database ID 5 at offset 0x0000000016c000 in file 'D:\MSSQL\IRIX.mdf'. 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 3313, Level 21, State 2, Line 1
During redoing of a logged operation in database 'IRIX', an error occurred at log record ID (844:9770:2). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Msg 3414, Level 21, State 1, Line 1
An error occurred during recovery, preventing the database 'IRIX' (database ID 5) 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.

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:182; actual 32:7602287). It occurred during a read of page (1:182) in database ID 5 at offset 0x0000000016c000 in file 'D:\MSSQL\IRIX.mdf'. 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.
During redoing of a logged operation in database 'IRIX', an error occurred at log record ID (844:9770:2). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
An error occurred during recovery, preventing the database 'IRIX' (database ID 5) 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.
Cannot drop the table '#tmp_sp_db_vardecimal_storage_format', because it does not exist or you do not have permission. (Microsoft SQL Server, Error: 824)

you make use of sp_resetstatus sp....just execute it and you need to restart sql services i believe...if its not working you can try,

just bring the db into emergency mode and you can extract the data alone to another db....
alter database DBNAME set emergency

and export the datas using ssis

|||

Oh dear, it's so easy... i've reset the status, bring it to emergency and exported the data...ALL! Amazing, thank you for your kind help.

CPU Ruuning at 100%

We have an instance of SQLRS on a virtual server under W2003.
Recently we had cause to reset the sever due to a dramatic slowdown in
response times. Upon checking we found the CPU usage was constantly around 95
to 100%.
Stopping the RS and SQL services made no difference and it was only resolved
by restarting the server itself.
This coincided with a user accessing an RS report with an Excel output,
which failed to respond 'fast enough' so he closed the window prior to the
dialogue box appearing (open-save-cancel).
We then set up a second server, and emulated exactly the users actions and
found the same problems with the CPU running out of control, requiring a
reset.
What might be the cause of this problem? I understand the user closing the
window initially caused the problem, but I am at a loss as to why stopping
the RS and SQL Services failed to resolve the problem. What other process
could RS have initiated that went out of control?
ANY pointers would be of use as this functionality is essential to some of
our processes, but we will need to restrict it's until this gets resolved.
Note: We have not, as yet, installed SP2 on either of the RS Servers.
Thanks in advance,We've ran into the same issues with high CPU usage. Support was never able
to point out the exact cause of the CPU spikes.
We have since installed all SPs, and the latest HotFix. So far, we haven't
seen the issue popup again. Maybe the SP2 helped with that, but we dont
know. It'll be good to know what causes it.
"Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
news:5DE74C28-B866-4F79-9E74-0539C6514E78@.microsoft.com...
> We have an instance of SQLRS on a virtual server under W2003.
> Recently we had cause to reset the sever due to a dramatic slowdown in
> response times. Upon checking we found the CPU usage was constantly around
> 95
> to 100%.
> Stopping the RS and SQL services made no difference and it was only
> resolved
> by restarting the server itself.
> This coincided with a user accessing an RS report with an Excel output,
> which failed to respond 'fast enough' so he closed the window prior to the
> dialogue box appearing (open-save-cancel).
> We then set up a second server, and emulated exactly the users actions and
> found the same problems with the CPU running out of control, requiring a
> reset.
> What might be the cause of this problem? I understand the user closing the
> window initially caused the problem, but I am at a loss as to why stopping
> the RS and SQL Services failed to resolve the problem. What other process
> could RS have initiated that went out of control?
> ANY pointers would be of use as this functionality is essential to some of
> our processes, but we will need to restrict it's until this gets resolved.
> Note: We have not, as yet, installed SP2 on either of the RS Servers.
> Thanks in advance,
>
>|||TechnoSpyke,
Thanks for the info. I intend setting up a test scenario and have the Server
guys run every trace they can to pinpoint what
process/subProcess/Application/Service is kicked off as a result of the said
actions.
I will post what results, if we get anything, even semi-conclusive, back to
this thread.
If anyone else has anything to chip in for me to check whilst testing this,
please feel free..
Thanks again
"TechnoSpyke" wrote:
> We've ran into the same issues with high CPU usage. Support was never able
> to point out the exact cause of the CPU spikes.
> We have since installed all SPs, and the latest HotFix. So far, we haven't
> seen the issue popup again. Maybe the SP2 helped with that, but we dont
> know. It'll be good to know what causes it.
>
> "Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
> news:5DE74C28-B866-4F79-9E74-0539C6514E78@.microsoft.com...
> > We have an instance of SQLRS on a virtual server under W2003.
> > Recently we had cause to reset the sever due to a dramatic slowdown in
> > response times. Upon checking we found the CPU usage was constantly around
> > 95
> > to 100%.
> > Stopping the RS and SQL services made no difference and it was only
> > resolved
> > by restarting the server itself.
> > This coincided with a user accessing an RS report with an Excel output,
> > which failed to respond 'fast enough' so he closed the window prior to the
> > dialogue box appearing (open-save-cancel).
> > We then set up a second server, and emulated exactly the users actions and
> > found the same problems with the CPU running out of control, requiring a
> > reset.
> > What might be the cause of this problem? I understand the user closing the
> > window initially caused the problem, but I am at a loss as to why stopping
> > the RS and SQL Services failed to resolve the problem. What other process
> > could RS have initiated that went out of control?
> > ANY pointers would be of use as this functionality is essential to some of
> > our processes, but we will need to restrict it's until this gets resolved.
> > Note: We have not, as yet, installed SP2 on either of the RS Servers.
> >
> > Thanks in advance,
> >
> >
> >
>
>