FIX: Dump File Handle Not Released After Error on Load Table

If SQL Server runs out of locks while loading a table, you will receive the following error: You cannot delete the dump file containing the table dump, and subsequent loads result in the following error: This occurs even after closing all connections to SQL Server.

You must stop and restart SQL Server before you can delete the dump file or load the table again. However, you will still be able to run other queries in SQL Server without having to stop and restart SQL Server.

See the SQL Server Books Online for the syntax of the LOAD TABLE command.

To work around this problem, increase the number of configured locks. For more information on how to do this, see the SQL Server Books Online.

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:For more information, contact your primary support provider.

After getting the error 1204, sp_who no longer shows the spid loading the table, and sp_lock no longer shows the ex_extent locks that were being held during the load. After closing all connections to SQL Server, the file properties for the dump file even show that there are no users with this file open, and that there are zero locks on the file.

However, you cannot delete this physical dump file or load the table, due to the following error: This error occurs because process cannot access the file; it is being used by another process.