BUG: INSERT...EXEC of TEXT/IMAGE value may cause 702

Last reviewed: April 8, 1997
Article ID: Q152805

The information in this article applies to:

Microsoft SQL Server, version 6.5

SYMPTOMS

Using INSERT..EXEC functionality within a stored procedure or trigger to insert a text/image value into a table may cause a 702 error, such as:

   Msg 702, Level 20, State 1
   Memory request for 4116 bytes exceeds the size of single page of 2044
   bytes.
   The SQL Server is terminating this process.

WORKAROUND

Run the entire INSERT..EXEC statement within a dynamic EXECUTE statement, for example:

   EXECUTE ('INSERT INTO t1 EXEC ("SELECT a FROM t2")')

STATUS

Microsoft has confirmed this to be a problem in Microsoft 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: Transact-SQL EXECUTE
Keywords : kbbug6.50
Version : 6.5
Platform : WINDOWS

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: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.