BUG: Error 705 If a LOAD TRAN Statement Is Within a T-SQL Loop

 Last reviewed: February 16, 1998
Article ID: Q176494
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 17379 (6.5)

SYMPTOMS

Successive transaction loads inside a loop may produce the following error: 

   Msg 705, Level 19, State 1
   There is no room for process %d to store PROC_HDR 0x%lx in Pss.
If you cycle the SQL Server after encountering the error 705, an error 624 is generated in syslogs. Either case makes the database suspect.

WORKAROUND

To work around this problem, do either of the following:

  • Do not perform a LOAD TRANSACTION statement inside a Transact-SQL loop.

    -or-

  • Use a scheduled task to do the LOAD TRANSACTION after each dump.

STATUS

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

Additional query words: tsql t-sql tran-sql trans-sql transql transsql
Keywords : kbbug6.50 SSrvProg SSrvTran_SQL kbprg
Version : WINNT:6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.