Microsoft KB Archive/319493

= FIX: SQL Server Stops Processing Results After First Error From Linked Server =

Article ID: 319493

Article Last Modified on 10/18/2005

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q319493



BUG #: 101522 (SQLBUG_70)



SYMPTOMS
If a linked server is used to call a procedure on a remote server, and the procedure returns an error higher than severity 10 that does not abort execution of the rest of the procedure or batch (generally any error less than severity 19), and there are any results or return values that should follow the error, the local SQL Server will not process the results or the return code. The query only returns results up to when the error occurs, and the return code is unavailable.

A good example of such an error message is a duplicate key error. For example:

Error 2627, Severity 14

Violation of PRIMARY KEY constraint 'test'. Cannot insert duplicate key in object 'test_table'



CAUSE
SQL Server does not continue to process results after it receives the first error from the remote source and the error is defined as something with severity 11 or higher.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:   Version      File name -

7.00.1024   Sqlservr.exe NOTE: Because of file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in Microsoft SQL Server 7.0.



MORE INFORMATION
With this fix, the local server changes the severity of errors from the remote source to severity 10 so that they are reported as informational messages only.

Keywords: kbbug kbfix kbqfe kbsqlserv700presp5fix kbhotfixserver KB319493

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.