Microsoft KB Archive/821537: Difference between revisions
(importing KB archive) |
m (Text replacement - ">" to ">") |
||
(One intermediate revision by the same user not shown) | |||
Line 115: | Line 115: | ||
This problem occurs when you perform an UPDATE operation or a DELETE operation, and SQL Server creates multiple sessions to the remote OLE DB provider to perform the operation. For example, when you run the following query, multiple sessions are created to perform the DELETE operation. | This problem occurs when you perform an UPDATE operation or a DELETE operation, and SQL Server creates multiple sessions to the remote OLE DB provider to perform the operation. For example, when you run the following query, multiple sessions are created to perform the DELETE operation. | ||
<pre class="codesample">DELETE FROM | <pre class="codesample">DELETE FROM <TableName> WHERE <ColumnName> = 10</pre> | ||
'''Note''' In this query, <code> | '''Note''' In this query, <code><TableName></code> is the table name, and <code><ColumnName></code> is the column name that is key to an index.<br /> | ||
<br /> | <br /> | ||
When you run this query, SQL Server creates a session to locate the record. SQL Server then creates another session to delete the record. The first session passes the bookmark that was obtained in the first session to the second session to perform the DELETE operation. Therefore, a deadlock condition is created between the two sessions.<br /> | When you run this query, SQL Server creates a session to locate the record. SQL Server then creates another session to delete the record. The first session passes the bookmark that was obtained in the first session to the second session to perform the DELETE operation. Therefore, a deadlock condition is created between the two sessions.<br /> |
Latest revision as of 10:21, 21 July 2020
Article ID: 821537
Article Last Modified on 11/2/2007
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 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (Windows)
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 469481 (SQL Server 8.0)
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package.
- The prerequisites for installing the hotfix package.
- Whether you must restart your computer after you install the hotfix package.
- Whether the hotfix package is replaced by any other hotfix package.
- The files that are contained in the hotfix package.
SYMPTOMS
When you try to perform an UPDATE operation or a DELETE operation against a remote OLE DB provider in Microsoft SQL Server 2000, a deadlock condition may occur. The deadlock condition may occur when the following conditions are true:
- The remote OLE DB provider is configured as a linked server that has the Index as Access Path option set.
Note When the Index as Access Path option is set, SQL Server uses the IRowsetIndex OLE DB interface to select the requested records.
- The remote OLE DB provider does not support the ICommand::Execute() method.
- The remote OLE DB provider only supports the IRowsetIndex interface and the IRowsetLocate interface.
- The isolation level is set to REPEATABLE READ or to a higher isolation level.
Note This problem does not occur if the isolation level is set to READ COMMITTED or to a lower isolation level.
For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:
290211 How to obtain the latest SQL Server 2000 service pack
CAUSE
This problem occurs when you perform an UPDATE operation or a DELETE operation, and SQL Server creates multiple sessions to the remote OLE DB provider to perform the operation. For example, when you run the following query, multiple sessions are created to perform the DELETE operation.
DELETE FROM <TableName> WHERE <ColumnName> = 10
Note In this query, <TableName>
is the table name, and <ColumnName>
is the column name that is key to an index.
When you run this query, SQL Server creates a session to locate the record. SQL Server then creates another session to delete the record. The first session passes the bookmark that was obtained in the first session to the second session to perform the DELETE operation. Therefore, a deadlock condition is created between the two sessions.
back to the top
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
Prerequisites
You must install SQL Server 2000 Service Pack 3 (SP3) to apply this hotfix. For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
Restart information
You do not have to restart your computer after you apply this hotfix.
back to the top
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
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 -------------------------------------------------------------- 18-Sep-2003 16:05 8.0.21213.0 352,256 Msvcr71.dll 18-Sep-2003 16:05 2000.80.796.0 57,904 Osql.exe 18-Sep-2003 16:05 2000.80.534.0 127,548 Sqdedev.dll 18-Sep-2003 16:05 2000.80.194.0 180,290 Sqlunirl.dll 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 12-Sep-2003 03:26 2000.80.859.0 1,905,216 Dtspkg.dll 26-Aug-2003 20:16 2000.80.854.0 528,960 Dtspump.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 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 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 12-Sep-2003 00:37 12,305 Qfe469315.sql 22-May-2003 22:57 19,195 Qfe469571.sql 06-Sep-2003 01:36 1,090,932 Replmerg.sql 06-Sep-2003 07:18 2000.80.858.0 221,768 Replprov.dll 06-Sep-2003 07:18 2000.80.858.0 307,784 Replrec.dll 06-Sep-2003 00:00 1,087,150 Replsys.sql 13-Aug-2003 16:28 986,603 Repltran.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 27-Sep-2003 04:42 2000.80.865.0 180,792 Sqlmap70.dll 03-Sep-2003 02:56 2000.80.857.0 188,992 Sqlmmc.dll 02-Sep-2003 23:03 2000.80.857.0 479,232 Sqlmmc.rll 08-Feb-2003 06:40 2000.80.765.0 57,920 Sqlrepss.dll 27-Sep-2003 04:42 2000.80.865.0 7,606,353 Sqlservr.exe 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 02-Jul-2003 00:19 2000.80.834.0 98,816 Xpweb70.dll 12-Sep-2003 03:26 2000.80.859.0 1,905,216 Dtspkg.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 03-Sep-2003 02:56 2000.80.857.0 188,992 Sqlmmc.dll 02-Sep-2003 23:03 2000.80.857.0 479,232 Sqlmmc.rll 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 that contains these files may also contain additional files.
back to the top
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.
back to the top
MORE INFORMATION
For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For additional information about the terminology that Microsoft uses to correct software after it is released, 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
Additional query words: SQL2000
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB821537