A bug in SQL Server 2000?

Hi!
I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
I've got a SQL Server Assertion: File:
<p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=
MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
CHECKDB of every DB on that server came up clean (0
allocation and 0 consistency errors). Could this
effectively mean that I've discovered a bug in SQL Server?
Thanks,
Osk
As you alluded to, this typically indicates corruption in your database.
However, there is a potential for in-memory kinds of corruption events in
which the page in memory is corrupted, but the image on disk is not. That
is most often caused by hardware issues. I would recommend that you open a
case with Microsoft PSS (http://support.microsoft.com) after you have
verified that you have no hardware issues.
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:243401c50d2a$2000fb90$a401280a@.phx.gbl...
> Hi!
> I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
> I've got a SQL Server Assertion: File:
> <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
> Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=
> MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
> CHECKDB of every DB on that server came up clean (0
> allocation and 0 consistency errors). Could this
> effectively mean that I've discovered a bug in SQL Server?
> --
> Thanks,
> Osk
>

A bug in SQL Server 2000?

Hi!
I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
I've got a SQL Server Assertion: File:
< p:\sql\ntdbms\storeng\drs\include\record
.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=
MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
CHECKDB of every DB on that server came up clean (0
allocation and 0 consistency errors). Could this
effectively mean that I've discovered a bug in SQL Server?
Thanks,
OskAs you alluded to, this typically indicates corruption in your database.
However, there is a potential for in-memory kinds of corruption events in
which the page in memory is corrupted, but the image on disk is not. That
is most often caused by hardware issues. I would recommend that you open a
case with Microsoft PSS (http://support.microsoft.com) after you have
verified that you have no hardware issues.
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:243401c50d2a$2000fb90$a401280a@.phx.gbl...
> Hi!
> I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
> I've got a SQL Server Assertion: File:
> < p:\sql\ntdbms\storeng\drs\include\record
.inl>, line=1447
> Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=
> MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
> CHECKDB of every DB on that server came up clean (0
> allocation and 0 consistency errors). Could this
> effectively mean that I've discovered a bug in SQL Server?
> --
> Thanks,
> Osk
>sql

A bug in SQL Server 2000?

Hi!
I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
I've got a SQL Server Assertion: File:
<p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
CHECKDB of every DB on that server came up clean (0
allocation and 0 consistency errors). Could this
effectively mean that I've discovered a bug in SQL Server?
--
Thanks,
OskAs you alluded to, this typically indicates corruption in your database.
However, there is a potential for in-memory kinds of corruption events in
which the page in memory is corrupted, but the image on disk is not. That
is most often caused by hardware issues. I would recommend that you open a
case with Microsoft PSS (http://support.microsoft.com) after you have
verified that you have no hardware issues.
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Osk" <anonymous@.discussions.microsoft.com> wrote in message
news:243401c50d2a$2000fb90$a401280a@.phx.gbl...
> Hi!
> I'm running MS Windows 2000 SP4 + SQL Server 2000 SP3a.
> I've got a SQL Server Assertion: File:
> <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
> Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=> MAXDATAROW'. Error: 3624, Severity: 20, State: 1. The
> CHECKDB of every DB on that server came up clean (0
> allocation and 0 consistency errors). Could this
> effectively mean that I've discovered a bug in SQL Server?
> --
> Thanks,
> Osk
>

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

3753 Provider is not specified and there is no designated default provider.

i just bought a brand new server and put windows server 2003 x64 sp1 on it then put sql server 2000 sp4 on that and set up a trusted odbc connection. however, it gave me the following error:
SQLSTATE:IM002, diagnosis:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
so i made a vbs file (adodb.connection) to see if that could connect to it and it came out with this on the err.number err.description
err.number = 3753
err.description = Provider is not specified and there is no designated default provider.
this even happened when i tried to use a dsnless connection to the old server machine so i dont know if its a problem with whatever is trying to use the connection or odbc or what. please can someone tell me what can i do to fix this problem?
i dont know if this is just a missing driver or something, odbc only has "SQL Server" in the list (C:\WINDOWS\System32\SQLSRV32.dll i think) wheras all my other machines have something like 25 or 30 drivers in the list, but "SQL Server" is the one im trying to use anyway..
edit: iis is not installed on this new server. other machines (with iis and vbs) can connect using dsnless or dsn with uid and pwd. also i think asp might have a different err.number for this problem than vbs' 3753

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

3455: Analysis of database is 100% complete

We're running SQL std. ed., v. 8.00.2039, SP4 using 'no-sync' replication (8
sites). In the Application log of the Event Viewer I get the following
message in groups of 3 every 15 minutes, "3455: Analysis of database
XXPROLAW' (7) is 100% complete (approximately 0 seconds)." I can't identify
what is triggering this analysis and it may be interferring with other
scheduled jobs causing them to fail. Couldn't find anything on Google or MS
N
K-base.
--
Steven PattonTry removing Auto Close from the database.
Found on another newsgroup and it works (but I don't know why).

3455: Analysis of database is 100% complete

We're running SQL std. ed., v. 8.00.2039, SP4 using 'no-sync' replication (8
sites). In the Application log of the Event Viewer I get the following
message in groups of 3 every 15 minutes, "3455: Analysis of database
XXPROLAW' (7) is 100% complete (approximately 0 seconds)." I can't identify
what is triggering this analysis and it may be interferring with other
scheduled jobs causing them to fail. Couldn't find anything on Google or MSN
K-base.
--
Steven PattonTry removing Auto Close from the database.
Found on another newsgroup and it works (but I don't know why).