FIX: Linked Server Query May Return NULL If It Is Performed Through a Keyset Cursor

Article translations Article translations
Article ID: 826860 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 470007 (SQL Server 8.0)
Expand all | Collapse all

On This Page

SYMPTOMS

A linked server query may return NULL for columns in its result set if all the following conditions are true:
  • The query is performed through a keyset cursor.
  • An OUTER JOIN is performed on 2 or more remote tables.
  • A 4-part name is used for each remote table.
  • All the remote tables that are related to the OUTER JOIN have unique indexes.
  • No rows are returned from inner tables of the OUTER JOIN clause.
For example, assume that you have the following data:
TableA
col1 col2
---- ----
   1    1

TableB
col1 col2
---- ----
   2    2
If you run the following query through a keyset cursor, this problem may occur:
SELECT * 
FROM rmtsvr.ownr.dbname.tableA A LEFT OUTER JOIN rmtsvr.ownr.dbname.tableB B
on A.col1=B.col1 and A.col2=B.col2

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time    Version           Size     File name
   --------------------------------------------------------------------
   31-May-2003  18:45   2000.80.818.0     78,400   Console.exe
   25-Jun-2003  01:01   2000.80.818.0     33,340   Dbmslpcn.dll
   25-Apr-2003  02:12                    786,432   Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296   Distmdl.mdf
   30-Jan-2003  01:55                        180   Drop_repl_hotfix.sql
   23-Jun-2003  22:40   2000.80.837.0  1,557,052   Dtsui.dll
   23-Jun-2003  22:40   2000.80.837.0    639,552   Dtswiz.dll
   24-Apr-2003  02:51                    747,927   Instdist.sql
   03-May-2003  01:56                      1,581   Inst_repl_hotfix.sql
   08-Feb-2003  06:40   2000.80.765.0     90,692   Msgprox.dll
   01-Apr-2003  02:07                      1,873   Odsole.sql
   05-Apr-2003  01:46   2000.80.800.0     62,024   Odsole70.dll
   07-May-2003  20:41   2000.80.819.0     25,144   Opends60.dll
   07-May-2003  18:47                    132,096   Opends60.pdb
   02-Apr-2003  21:48   2000.80.796.0     57,904   Osql.exe
   02-Apr-2003  23:15   2000.80.797.0    279,104   Pfutil80.dll
   04-Aug-2003  18:17                    550,780   Procsyst.sql
   22-May-2003  22:57                     19,195   Qfe469571.sql
   11-Jul-2003  17:04                  1,084,147   Replmerg.sql
   04-Apr-2003  21:53   2000.80.798.0    221,768   Replprov.dll
   08-Feb-2003  06:40   2000.80.765.0    307,784   Replrec.dll
   11-Jul-2003  16:56                  1,085,925   Replsys.sql
   29-Jul-2003  20:13   2000.80.819.0    492,096   Semobj.dll
   31-May-2003  18:27   2000.80.818.0    172,032   Semobj.rll
   05-Aug-2003  21:06                    127,884   Sp3_serv_uni.sql
   01-Jun-2003  01:01   2000.80.818.0  4,215,360   Sqldmo.dll
   07-Apr-2003  17:44                     25,172   Sqldumper.exe
   19-Mar-2003  18:20   2000.80.789.0     28,672   Sqlevn70.rll
   02-Jul-2003  00:18   2000.80.834.0    180,736   Sqlmap70.dll
   08-Feb-2003  06:40   2000.80.765.0     57,920   Sqlrepss.dll
   07-Aug-2003  19:11   2000.80.850.0  7,598,164   Sqlservr.exe
   07-Aug-2003  19:11                 12,755,968   Sqlservr.pdb
   25-Jul-2003  21:44   2000.80.845.0    590,396   Sqlsort.dll
   08-Feb-2003  06:40   2000.80.765.0     45,644   Sqlvdi.dll
   25-Jun-2003  01:01   2000.80.818.0     33,340   Ssmslpcn.dll
   01-Jun-2003  01:01   2000.80.818.0     82,492   Ssnetlib.dll
   01-Jun-2003  01:01   2000.80.818.0     25,148   Ssnmpn70.dll
   01-Jun-2003  01:01   2000.80.818.0    158,240   Svrnetcn.dll
   31-May-2003  18:59   2000.80.818.0     76,416   Svrnetcn.exe
   30-Apr-2003  23:52   2000.80.816.0     45,132   Ums.dll
   30-Apr-2003  23:52                    132,096   Ums.pdb
   02-Jul-2003  00:19   2000.80.834.0     98,816   Xpweb70.dll
   23-Jun-2003  22:40   2000.80.837.0  1,557,052   Dtsui.dll
   23-Jun-2003  22:40   2000.80.837.0    639,552   Dtswiz.dll
   02-Apr-2003  21:48   2000.80.796.0     57,904   Osql.exe
   02-Apr-2003  23:15   2000.80.797.0    279,104   Pfutil80.dll
   29-Jul-2003  20:13   2000.80.819.0    492,096   Semobj.dll
   31-May-2003  18:27   2000.80.818.0    172,032   Semobj.rll
   01-Jun-2003  01:01   2000.80.818.0  4,215,360   Sqldmo.dll
   07-Apr-2003  17:44                     25,172   Sqldumper.exe
   01-Jun-2003  01:01   2000.80.818.0    158,240   Svrnetcn.dll
   31-May-2003  18:59   2000.80.818.0     76,416   Svrnetcn.exe

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.


Note This hotfix must be applied to a local server, not to a remote server.

WORKAROUND

To work around this problem, use one of the following methods:
  • Use a static cursor instead of a keyset cursor.
  • Use a pass-through query instead of a 4-part name query. To do so, you can use either of the following Transact-SQL functions:
    • OPENQUERY
    • OPENROWSET
  • Use an ad-hoc query instead of a cursor.
  • If you can, change unique indexes to non-unique indexes on the remote tables. This changes the cursor type to static.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 826860 - Last Review: February 27, 2014 - Revision: 8.3
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbsqlserv2000presp4fix kbfix kbbug KB826860

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com