database attach error

fellows,
I have some problems!!!!!! I was given a database that is in rough shape. here are the particulars. SQL 2000 RTM. The SQL Services wouldn't start the database when the engine came up. Here is where it gets shaky. They say that they dettached the database
when it was in "emergency" mode now they have nothing. No service packs, no maintenance, and a datbase that won't start. When I try to attach i get this nasty error.
Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
SPID: 55
Process ID: 2068
Connection Broken
I have tried sp_attach_single_file_db but do not have the same directory structure so it continues to error out.
Does any one have any ideas on how to attach just so I can read or script? Then maybe I can export / import ?
I think you're going to have to call MS support... When you get a debug
error you know something really bad has happened.
"detroit" <sbowman@.broward.org> wrote in message
news:72CB734D-6E7E-482C-A09B-F1BEE2AAE948@.microsoft.com...
> fellows,
> I have some problems!!!!!! I was given a database that is in rough shape.
here are the particulars. SQL 2000 RTM. The SQL Services wouldn't start the
database when the engine came up. Here is where it gets shaky. They say that
they dettached the database when it was in "emergency" mode now they have
nothing. No service packs, no maintenance, and a datbase that won't start.
When I try to attach i get this nasty error.
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recbase.cpp:1378
> Expression: m_offBeginVar < m_SizeRec
> SPID: 55
> Process ID: 2068
> Connection Broken
> I have tried sp_attach_single_file_db but do not have the same directory
structure so it continues to error out.
>
> Does any one have any ideas on how to attach just so I can read or script?
Then maybe I can export / import ?
>
|||Create a new database with the same name and file names in a different
directory than the current MDF and LDF files. After you create the new
database, stop SQL Server and copy the old database files over the top of
the new ones. SQL Server will recognize the database. It may set the
suspect status but then you can put it in emergency mode and try to extract
whatever data out of it. Or run DBCC Checkdb and see if it can be repaired.
Rand
This posting is provided "as is" with no warranties and confers no rights.