November 3, 2008 at 1:11 pm
I found this info :
http://www.sqlservercentral.com/Forums/Topic113708-5-1.aspx#bm113715
But I can't run anything against the database because I don't have it attached...
November 3, 2008 at 1:19 pm
Sorry for spamming my thread! Urgency making my thread somewhat frantic :)---
Customer is on SP3....looks like SP4 may resolve that error?
November 3, 2008 at 1:24 pm
That looks like a runtime error, did it just pop up during recovery or?
I think you have some serious corruption issues; you absolutely have to run DBCC CHECKDB on your databases. You might have to set one or some of them (that won't go through Recovery) in Emergency mode in order to run DBCC CHECKDB.
While those are running, get your backups ready and if I were you, I would seriously start to look for an alterntive disk location for my databases 😛
/Elisabeth
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
November 3, 2008 at 1:27 pm
Thanks for your response!
There are only 2 databases on this customer's server. 1 has been restored correctly and error checking reported no errors.
As for the error, I found this microsoft article:
http://support.microsoft.com/?kbid=827714
When you run a query with the NOLOCK hint or with the transaction isolation level set to READ UNCOMMITTED, and a concurrent user is deleting rows from the table that is accessed by the query, the query may fail with a retail assertion, and you may receive an assertion error message that is similar to the following:
Msg 3624
Location: Drive:\sqltdbms\storeng\drs\include\record.inl:1447
Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW
SPID: 63
Process ID: 1776
That sounds like my error. The fix suggested is to install SP4....Any input?
November 3, 2008 at 1:29 pm
To support my doomsday theory : http://support.microsoft.com/kb/828337 "An assertion or Msg 7987 may occur when an operation is performed on an instance of SQL Server"
/Elisabeth
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
November 3, 2008 at 1:30 pm
Elisabeth Rédei (11/3/2008)
did it just pop up during recovery or?
/Elisabeth
That error pops up during my attempt to Attach the second database.
When I restored the system dbs, obviously I lost all attached databases so I tried attaching via GUI in Enterprise Manager...
I am wondering if there's a way to check a raw MDF file without it being attached to anything? Is that bass akwards?
November 3, 2008 at 1:46 pm
Nah, you can't. So no backup available? Of user db or master?
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
November 3, 2008 at 1:50 pm
They are "having issues" with their backup service.
That's all I've been able to get out of them other than their apparent urgency to get this up and running somehow without the backups.
Sounds like they may have effed up in the backup department...
November 3, 2008 at 2:06 pm
Yes it certainly does. Well, I am going offline now but it seems like you have things in control.
If you find a backup of the user database - great. If you find a master backup (that already points to your user database files) you might be able to set that userdb in Emergency mode and take it from there.
If none of the above; I think you know where you are 😉
/Elisabeth
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
November 3, 2008 at 2:10 pm
you are awesome Elizabeth 😀
Cheers,
John Esraelo
November 3, 2008 at 2:28 pm
Alright, well we'll have to see where I can get 🙂
Thanks so much for your help!
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply