Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>
Hi Marco,
There are two possibilities: either your disk media is giving you problems
restoring or your mdf file itself is corrupt beyond recovery.
Can you copy the database files to on another physical drive and then
attach from that path or from another SQL Server machine that you know has
a good healthy disk system? We are trying to eliminate your raid system as
the root cause of the Error 823.
If your database files won't attach from a clean disk system, then it is
corrupt beyond recovery. Your best option in this situation is to restore
from your last good backup.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais
Please don't post the same question to multiple groups.
My answer from .tools:
You can't correct this error - its a hard error with the underlying disk
(i.e. the OS tells SQL Server it can't read the bytes off the disk). You'll
need to suck as much data out of the database as you can onto new media. I
would contact PSS to help you (http://support.microsoft.com)
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:eS4R5t2PEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>
--
Hi Marco,
There are two possibilities: either your disk media is giving you problems
restoring or your mdf file itself is corrupt beyond recovery.
Can you copy the database files to on another physical drive and then
attach from that path or from another SQL Server machine that you know has
a good healthy disk system? We are trying to eliminate your raid system as
the root cause of the Error 823.
If your database files won't attach from a clean disk system, then it is
corrupt beyond recovery. Your best option in this situation is to restore
from your last good backup.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco PaisPlease don't post the same question to multiple groups.
My answer from .tools:
You can't correct this error - its a hard error with the underlying disk
(i.e. the OS tells SQL Server it can't read the bytes off the disk). You'll
need to suck as much data out of the database as you can onto new media. I
would contact PSS to help you (http://support.microsoft.com)
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:eS4R5t2PEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>sql

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais
You can't correct this error - its a hard error with the underlying disk
(i.e. the OS tells SQL Server it can't read the bytes off the disk). You'll
need to suck as much data out of the database as you can onto new media. I
would contact PSS to help you (http://support.microsoft.com)
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:u34zmu2PEHA.2132@.TK2MSFTNGP11.phx.gbl...
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>
|||Hi...
I cannot extract much data out of the database and I can't view the most
important tables data. i get allways the same error.
I've tried to attach the database in a brand new computer, with a fresh
instance of SQL Server. The problem is in the .MDF file, i gess. Is there
any tool that repair (or try to) .MDF files?
Thanks again...
Regards
"Paul S Randal [MS]" <prandal@.online.microsoft.com> escreveu na mensagem
news:%234c1x02PEHA.640@.TK2MSFTNGP12.phx.gbl...
> You can't correct this error - its a hard error with the underlying disk
> (i.e. the OS tells SQL Server it can't read the bytes off the disk).
You'll
> need to suck as much data out of the database as you can onto new media. I
> would contact PSS to help you (http://support.microsoft.com)
> Regards.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Marco Pais" <mpais@.foruminformatica.pt> wrote in message
> news:u34zmu2PEHA.2132@.TK2MSFTNGP11.phx.gbl...
> hardware
> recently
> is,
in[vbcol=seagreen]
but[vbcol=seagreen]
> that
to[vbcol=seagreen]
cannot
>
|||I suspect you're not going to get much out of this - why you should always
have a comprehensive, tested backup strategy.
I recommend calling PSS to help you (http://support.microsoft.com) as
there's nothing that can be done over the newsgroups.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:#YeRze3PEHA.832@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi...
> I cannot extract much data out of the database and I can't view the most
> important tables data. i get allways the same error.
> I've tried to attach the database in a brand new computer, with a fresh
> instance of SQL Server. The problem is in the .MDF file, i gess. Is there
> any tool that repair (or try to) .MDF files?
> Thanks again...
> Regards
>
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> escreveu na mensagem
> news:%234c1x02PEHA.640@.TK2MSFTNGP12.phx.gbl...
> You'll
I[vbcol=seagreen]
> rights.
0.[vbcol=seagreen]
company.[vbcol=seagreen]
problem[vbcol=seagreen]
the[vbcol=seagreen]
0x0000001ef3c000[vbcol=seagreen]
> in
far,
> but
> to
> cannot
>

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco Pais
[posted and mailed, please reply in news]
Marco Pais (mpais@.foruminformatica.pt) writes:
> A month ago a compaq server hosting a SQL Server 2000 Server had a
> hardware crash. Unfortunatly, the Compaq Smart Array was configured with
> RAID 0.
> Aparently the problem was there a long time ago and there was not a
> recently backup file. So, we've delivered the Raid System to a Recovery
> company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
> is, after i attach the database to a clean instance of Sql Server, i get
> the following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
Open a case with Microsoft Support. It looks as if your database is
corrupt, and to get back in order is no easy task.

> How can I resove this problem? I have read thousands of Forum messages
> but i've no solution. I have read Microsoft Knowledge Base Article
> 826433, that tells me that there are a build of Sql server, wich have
> several tools to try to correct this problem. Tha leads me to another
> problem... i cannot find that file versions.
That's right. Most hotfixes are not downloadable, but you need to
open a case with Microsoft to get hold of them. This is also detailed
in all KB articles which announces hotfixes.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Error 823

Hello.
I pray to that someone can help me...
A month ago a compaq server hosting a SQL Server 2000 Server had a hardware
crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
Aparently the problem was there a long time ago and there was not a recently
backup file. So, we've delivered the Raid System to a Recovery company.
The data was recovered, I have the .MDF and the .LDF files. The problem is,
after i attach the database to a clean instance of Sql Server, i get the
following error:
******************
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
file 'D:\Data\database_Data.MDF'.
Connection Broken
******************
I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
with no results.
How can I resove this problem? I have read thousands of Forum messages but
i've no solution. I have read Microsoft Knowledge Base Article 826433, that
tells me that there are a build of Sql server, wich have several tools to
try to correct this problem. Tha leads me to another problem... i cannot
find that file versions.
I would thanks any solution, any help.
Regards.
Marco PaisPlease don't post the same question to multiple groups.
My answer from .tools:
You can't correct this error - its a hard error with the underlying disk
(i.e. the OS tells SQL Server it can't read the bytes off the disk). You'll
need to suck as much data out of the database as you can onto new media. I
would contact PSS to help you (http://support.microsoft.com)
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Pais" <mpais@.foruminformatica.pt> wrote in message
news:eS4R5t2PEHA.1392@.TK2MSFTNGP09.phx.gbl...
> Hello.
> I pray to that someone can help me...
> A month ago a compaq server hosting a SQL Server 2000 Server had a
hardware
> crash. Unfortunatly, the Compaq Smart Array was configured with RAID 0.
> Aparently the problem was there a long time ago and there was not a
recently
> backup file. So, we've delivered the Raid System to a Recovery company.
> The data was recovered, I have the .MDF and the .LDF files. The problem
is,
> after i attach the database to a clean instance of Sql Server, i get the
> following error:
> ******************
> Server: Msg 823, Level 24, State 2, Line 1
> I/O error (bad page ID) detected during read at offset 0x0000001ef3c000 in
> file 'D:\Data\database_Data.MDF'.
> Connection Broken
> ******************
> I've tried several possible solutions as CHECKDB, CHECKALLOC and so far,
> with no results.
> How can I resove this problem? I have read thousands of Forum messages but
> i've no solution. I have read Microsoft Knowledge Base Article 826433,
that
> tells me that there are a build of Sql server, wich have several tools to
> try to correct this problem. Tha leads me to another problem... i cannot
> find that file versions.
> I would thanks any solution, any help.
> Regards.
> Marco Pais
>

Error 3624 recbase.cpp:1374 m_nVars > 0

Hello out there...
unfortunatly I am not (yet) a SQL Server pro, so I need some help:
Some days ago we had a Server crash. The Server was running fine but
after a reboot the ntloader was gone - forever... After much work we
gained access to the harddisk which we checked with chkdsk. This took
more than 2 hours but after that we were able to make an image of the
harddisks with acronis true image.
I extracted the two databasefiles .mdf and .ldf from this image and
tryed to attach the database on the new installed system. The
attchement process finished fine, but when trying to access the
properties of the db I get this error:
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
[Microsoft][ODBC SQL Server Driver][SQL Server]
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 60
Process ID: 2052
Some googling pointed out that the db seems to be corrupt. I saw many
posts with DBCC commands, but untill now I dont know how and where to
use them. Can anyone give me some help howto repair the database?
I=B4m using MS SQL 2000 SP3 and tryed also SP4. More informations on
demand.Hi
If you are referring to:
http://groups.google.com/group/micr...00fea7f4929049b
which mentions DBCC CHECKDB. This can be run from Query Analyser, which
should be on the start menu. Starting the application will give you a login
dialog. Once logged in you can run the command
DBCC CHECKDB ( 'database_name' )
To run this command you need to be the database owner or a sysadmin. If you
are the local system administrator and logged on using windows authenticatio
n
then you should be ok, if not, you may want to try logging in as sa .
John
]
"bilbogm@.gmx.de" wrote:

> Hello out there...
> unfortunatly I am not (yet) a SQL Server pro, so I need some help:
> Some days ago we had a Server crash. The Server was running fine but
> after a reboot the ntloader was gone - forever... After much work we
> gained access to the harddisk which we checked with chkdsk. This took
> more than 2 hours but after that we were able to make an image of the
> harddisks with acronis true image.
> I extracted the two databasefiles .mdf and .ldf from this image and
> tryed to attach the database on the new installed system. The
> attchement process finished fine, but when trying to access the
> properties of the db I get this error:
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 60
> Process ID: 2052
> Some googling pointed out that the db seems to be corrupt. I saw many
> posts with DBCC commands, but untill now I dont know how and where to
> use them. Can anyone give me some help howto repair the database?
> I′m using MS SQL 2000 SP3 and tryed also SP4. More informations on
> demand.
>

Error 3624 recbase.cpp:1374 m_nVars > 0

Hello out there...
unfortunatly I am not (yet) a SQL Server pro, so I need some help:
Some days ago we had a Server crash. The Server was running fine but
after a reboot the ntloader was gone - forever... After much work we
gained access to the harddisk which we checked with chkdsk. This took
more than 2 hours but after that we were able to make an image of the
harddisks with acronis true image.
I extracted the two databasefiles .mdf and .ldf from this image and
tryed to attach the database on the new installed system. The
attchement process finished fine, but when trying to access the
properties of the db I get this error:
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
[Microsoft][ODBC SQL Server Driver][SQL Server]
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 60
Process ID: 2052
Some googling pointed out that the db seems to be corrupt. I saw many
posts with DBCC commands, but untill now I dont know how and where to
use them. Can anyone give me some help howto repair the database?
I=B4m using MS SQL 2000 SP3 and tryed also SP4. More informations on
demand.
Hi
If you are referring to:
http://groups.google.com/group/micro...0fea7f4929049b
which mentions DBCC CHECKDB. This can be run from Query Analyser, which
should be on the start menu. Starting the application will give you a login
dialog. Once logged in you can run the command
DBCC CHECKDB ( 'database_name' )
To run this command you need to be the database owner or a sysadmin. If you
are the local system administrator and logged on using windows authentication
then you should be ok, if not, you may want to try logging in as sa .
John
]
"bilbogm@.gmx.de" wrote:

> Hello out there...
> unfortunatly I am not (yet) a SQL Server pro, so I need some help:
> Some days ago we had a Server crash. The Server was running fine but
> after a reboot the ntloader was gone - forever... After much work we
> gained access to the harddisk which we checked with chkdsk. This took
> more than 2 hours but after that we were able to make an image of the
> harddisks with acronis true image.
> I extracted the two databasefiles .mdf and .ldf from this image and
> tryed to attach the database on the new installed system. The
> attchement process finished fine, but when trying to access the
> properties of the db I get this error:
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 60
> Process ID: 2052
> Some googling pointed out that the db seems to be corrupt. I saw many
> posts with DBCC commands, but untill now I dont know how and where to
> use them. Can anyone give me some help howto repair the database?
> I′m using MS SQL 2000 SP3 and tryed also SP4. More informations on
> demand.
>

Error 3624 recbase.cpp:1374 m_nVars > 0

Hello out there...
unfortunatly I am not (yet) a SQL Server pro, so I need some help:
Some days ago we had a Server crash. The Server was running fine but
after a reboot the ntloader was gone - forever... After much work we
gained access to the harddisk which we checked with chkdsk. This took
more than 2 hours but after that we were able to make an image of the
harddisks with acronis true image.
I extracted the two databasefiles .mdf and .ldf from this image and
tryed to attach the database on the new installed system. The
attchement process finished fine, but when trying to access the
properties of the db I get this error:
[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
[Microsoft][ODBC SQL Server Driver][SQL Server]
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 60
Process ID: 2052
Some googling pointed out that the db seems to be corrupt. I saw many
posts with DBCC commands, but untill now I dont know how and where to
use them. Can anyone give me some help howto repair the database?
I=B4m using MS SQL 2000 SP3 and tryed also SP4. More informations on
demand.Hi
If you are referring to:
http://groups.google.com/group/microsoft.public.sqlserver.server/browse_frm/thread/9681aa08dd8a58eb/400fea7f4929049b#400fea7f4929049b
which mentions DBCC CHECKDB. This can be run from Query Analyser, which
should be on the start menu. Starting the application will give you a login
dialog. Once logged in you can run the command
DBCC CHECKDB ( 'database_name' )
To run this command you need to be the database owner or a sysadmin. If you
are the local system administrator and logged on using windows authentication
then you should be ok, if not, you may want to try logging in as sa .
John
]
"bilbogm@.gmx.de" wrote:
> Hello out there...
> unfortunatly I am not (yet) a SQL Server pro, so I need some help:
> Some days ago we had a Server crash. The Server was running fine but
> after a reboot the ntloader was gone - forever... After much work we
> gained access to the harddisk which we checked with chkdsk. This took
> more than 2 hours but after that we were able to make an image of the
> harddisks with acronis true image.
> I extracted the two databasefiles .mdf and .ldf from this image and
> tryed to attach the database on the new installed system. The
> attchement process finished fine, but when trying to access the
> properties of the db I get this error:
> [Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3624:
> [Microsoft][ODBC SQL Server Driver][SQL Server]
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 60
> Process ID: 2052
> Some googling pointed out that the db seems to be corrupt. I saw many
> posts with DBCC commands, but untill now I dont know how and where to
> use them. Can anyone give me some help howto repair the database?
> I´m using MS SQL 2000 SP3 and tryed also SP4. More informations on
> demand.
>