Post reply

SQL Server Assertion

  • April 30, 2009 at 1:39 am

    #208765

    Hi all,

    Last night, my production server generated an error;

    "could not find an entry for table or index with partition ID XX in database 2. This error can occur if a stored procedure references a dropped table

    or metadata is corrupt. Drop and re-create the stored procedure, or execute DBCC CHECKDB."

    I've personally never come across this error before and I was just looking to see if anyone had any information that may help me diagnose the cause and potential solution.

    We have run a CHECKDB and found no issues with any of the databases, the error also does not appear to of cause any loss of data or availability of data. The server did a stack dump however the file generated just indicates a large amount of memory being used.

    Any help would be appreciated.

    Thanks,

    Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

  • April 30, 2009 at 3:27 am

    #986513

    well first the issue is with TempDB. I would suggest follow Kb937343 might be we are hiting a bug. apply SP3 and do a regression testing and if that helps go ahead.

  • April 30, 2009 at 3:39 am

    #986517

    Thanks for the reply nilmov,

    I'm currently looking into the KB 937343, hopefully this will should resolve the issues.

    Thanks again.

    Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

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

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