Post reply

Error: 832, Severity: 24, State: 1.

  • August 17, 2010 at 2:49 am

    #1207702

    You've either got bad memory or there's a memory scribbler somewhere (kernel process or something in-process with SQL that's changing SQL's memory)

    To say this is bad is an understatement. It can cause all sorts of problems, including data corruption, SQL crashes, etc. An error of that severity will kill the connection that encountered it

    I suggest that you do some hardware diagnostics, focused on memory especially.

    Do you have any custom extended stored procedures?

    Any in-process linked server drivers?

    Any unusual kernel drivers (operating system level)?

    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

  • August 17, 2010 at 3:03 am

    #1207706

    Thank you for a quick reply. I donot have any custom extended stored procedures or in process linked servers.

    So do this kind of errors impact data inserts into a table inside a transaction? When I run CHECKDB on the database I got two inconsistency errors but this have no reference to the table on which the insert failed.

    Msg 8914, Level 16, State 1, Line 1

    Incorrect PFS free space information for page (1:6696) in object ID 1600724755, index ID 0, partition ID 72057594055557120, alloc unit ID 72057594063486976 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

    Msg 8914, Level 16, State 1, Line 1

    Incorrect PFS free space information for page (1:13734) in object ID 1600724755, index ID 0, partition ID 72057594055557120, alloc unit ID 72057594063486976 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

    Regards

    Prasad Bhogadi
    www.inforaise.com

  • August 17, 2010 at 3:14 am

    #1207709

    That kind of error can affect just about anything. It's saying that something is changing SQL's memory outside of its control.

    Are you the DBA? The checkDB errors aren't severe but, combined with the error 832 indicates that there are some very serious problems with that server that need to be investigated.

    I suggest that you escalate this to the senior DBA there.

    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

  • August 17, 2010 at 3:20 am

    #1207713

    Thank you.

    Prasad Bhogadi
    www.inforaise.com

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

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