Knowledge Base

BUG: Repeated Deadlocks May Cause Error 925

PSS ID Number: 122953

Article Last Modified on 4/18/1999

The information in this article applies to:

Microsoft SQL Server 4.2x

This article was previously published under Q122953

BUG# NT: 939 (4.2)

SYMPTOMS

A call to a stored procedure that in turn calls another stored procedure can, in some cases, generate error 925:

Maximum number of used databases for each query has been exceeded.
The maximum allowed is %d.

CAUSE

SQL Server is not correctly freeing the data structures used to maintain information for each database when the called stored procedure fails with a deadlock.

WORKAROUND

Reestablish your connection to SQL Server in order to get a new spid.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Given two stored procedures, CALLED and CALLER, where procedure CALLED is called by procedure CALLER error 925 will occur if:

Procedure CALLER and procedure CALLED exist in two separate databases.
Procedure CALLER calls procedure CALLED repeatedly utilizing the same connection to the server (spid).
Procedure CALLED fails because of a deadlock that generates error 1205:
Your server command (process id #%d) was deadlocked with another
process and has been chosen as deadlock victim. Re-run your command.

Additional query words: Windows NT

Keywords: kbprogramming KB122953
Technology: kbAudDeveloper kbSQLServ420 kbSQLServSearch