assertion error

  • I load heavily every week.This week for the first time I got this err:

    SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447

    Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.

    ... followed bu and I/O error, followed by process stop

    Now, I ran DBCC at no avail;I am going to restore.But the point is - Is it possible when we insert new data, that data to corrupt the index in tables?

    and the second question ==>> I do not have a drive p and still the error points to a drive p.I have checked the INternet and I have found the same error in different cases.but what is the semnificance of drive p where there is none?

    Respectfully,

    LMT

  • p:\sql\ntdbms\storeng\drs\include\record.inl looks like a bug in some inline function deep inside SQL Server.

    If it is reproducable ?!? I would call MS support.

    Frank

    http://www.insidesql.de

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply