Microsoft KB Archive/300195

From BetaArchive Wiki
Knowledge Base


Article ID: 300195

Article Last Modified on 10/9/2003



APPLIES TO

  • Microsoft SQL Server 2000 Standard Edition



This article was previously published under Q300195

BUG #: 353569 (SHILOH_BUGS)

SYMPTOMS

When the following conditions are true, the SQL Distributed Management Objects (SQL-DMO) Transfer method fails to copy all the data, but nevertheless reports success:

  • The tables contain more than 1000 rows.
  • An error occurs while reading the data from the source beyond the 1000th row.

NOTE: The "Copy SQL Server Objects" Data Transformation Services (DTS) task also uses the SQL-DMO Transfer method.

CAUSE

The SQL-DMO Transfer method does not handle read errors correctly under the circumstances listed in the "Symptoms" section of this article.

RESOLUTION

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 INF: How to Obtain the Latest SQL Server 2000 Service Pack


Hotfix

NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.

The English version of this fix should have the following file attributes or later:

   Date          Time    Version    Size      File name    Platform
   ----------------------------------------------------------------
   17-May-2001   21:12   8.00.293   4194368   Sqldmo.dll   Intel
   17-May-2001   21:12   8.00.293     94272   Sqlsvc.dll   Intel
                

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.


WORKAROUND

Before you transfer the data with SQL-DMO, make sure that all that data can be read from the source tables. For example, this code:

 SELECT * FROM ... 
                

should successfully return all the rows and no error message.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix kbsqlserv2000presp2fix KB300195