Microsoft KB Archive/276992

= FIX: Bulk Insert or Snapshot Replication May Corrupt Table During NOLOCK Scans =

Article ID: 276992

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q276992



BUG #: 58015 (SQLBUG_70)



SYMPTOMS
Performing a bulk insert in a table using the TABLOCK hint while other clients run some NOLOCK or Read Uncommitted scans on same table may corrupt the table.

This problem may also occur with snapshot replication on the subscribers, because it uses a bulk insert statement with a TABLOCK hint.

Read Uncommitted scans will fail with the following error message:

Server: Msg 601, Level 12, State 3, Line 1

Could not continue scan with NOLOCK due to data movement.

The bulk insert operation may end successfully, generate an access violation (AV) or produce error 605.

Running a DBCC CHECKTABLE statement may find errors 2535, 8951, 8955, 8952, or 8956.



WORKAROUND
To work around this problem, do not use the TABLOCK hint with a bulk insert if the table may be scanned by uncommitted transactions at same time.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Additional query words: repl

Keywords: kbbug kbfix KB276992

-

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

© Microsoft Corporation. All rights reserved.