Tuesday, March 20, 2012

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
>

No comments:

Post a Comment