Error [36, 17, 145] occurred while attempting to drop allocation unit ID xxx belonging to worktable with partition ID yyy.

  • On one of our production SQL Servers, we sometimes get a message / messages in the SQL Server Error Log like this

    2016-10-13 09:40:42.21 spid234 Error [36, 17, 145] occurred while attempting to drop allocation unit ID 448755325140992 belonging to worktable with partition ID 448755325140992.

    This corresponds to a period of slow performance for a period of ten minutes or so. There are often several similar messages for different allocation unit ID / partition ID. There is nothing in the windows event logs that corrolate with this.

    Can anybody advise me what might be causing this? Or what it means?

    If not, have you any advice as to how to gather any further details 'after the event' to determine what the SPID was doing at the time?

    Thanks in anticipation

    Tim

    .

  • Here is a previous post where Gail suggested running checkdb.

    http://www.sqlservercentral.com/Forums/Topic1682406-2799-1.aspx

    Also, here is Microsoft topic where they suggest patching to latest SP or CU.

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ae0e6f71-ff63-49ee-bcaf-c53fa4dea6e4/error36-17-145-occurred-while-attempting-to-drop-allocation-unit?forum=sqldatabaseengine

    Catch-all queries done right [/url]
    Gail Shaw's Performance Blog[/url]

  • Thanks MadAdmin.

    We run regular CHECKDB and it comes back OK. The system has been rebooted and the issue persists.

    It's SQL Server 2012 Enterprise Edition Service Pack 3 (but we had the same error on Service Pack 1 too) running on Windows Server 2012 R2.

    I suspect we have a very heavy process that prompts this to happen.

    Any tips on how to find out what this process is after the event would be much appreciated.

    Thanks

    Tim

    .

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

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