Post reply

SQL Dump Exception

  • December 5, 2006 at 8:23 am

    #175172

    Hi ,

     

    Not sure if this is under the correct section.

    We have several applications running from a single database. These have been running with no real problems for about 3 years.

    However in the last couple of months, about once a week/fortnight some of the applications fall over.

    The error msg in the log is:

    Using 'dbghelp.dll' version '4.0.5'

    error: 0 , severity: 19, state 0

    Sqldumpexceptionhandler process 133 generated fatal exception c0000005.

     

    We currently fix this problem by select * into newtable from corrupttable, rename the new table with actual and corrupt with another name.

    We then have to recreate primary key and add in any defaults.

    This works as a short term fix.

     

    We think we have located the query causing this by running a trace, but it doesnt happen every time its run. The only thing is it has several *= clauses in it.

     

    Any help would be greatly appretiated

     

    Thanks

     

    Andy

  • December 5, 2006 at 8:28 am

    #675880

    I'd go with your hunch at this point (cause I have none of my own ).

     

    Try changing to left/right join syntaxe for the 2000 servers and see if that helps.

  • December 5, 2006 at 8:29 am

    #675882

    Have you run the dbcc check db() and other dbcc commands to see if anything comes ups.

     

    Any possibilities that the disk may be corrupted (doubt it but I got nothing else to offer).

  • December 6, 2006 at 1:16 am

    #676143

    If all else fails, contact Microsoft PSS. They'll be able to read the stack dume and (hopefully) find the cause and a solution.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 6, 2006 at 11:53 am

    #676365

    What version and build you are on?

    Did you check mini dump files?

    You may see procedure info in dump files if it is caused by the user proc.

    For exception  and acces voilation errors, it is better to call PSS...

     

    MohammedU
    Microsoft SQL Server MVP

Viewing 5 posts - 1 through 4 (of 4 total)

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