Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DTS error during import 1

Status
Not open for further replies.

mmetze

Programmer
Oct 2, 2001
45
US
I have a table which I cannot import data into. This table contains a column of type 'timestamp'- which may or may not be the culprit. I can even export the data from this table to a comma-delimited flat file, delete the rows from the table and then try to import them back into the same table from the flat file, and the following error occurs...

Multi-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

I have tried reducing this table to a single row and repeating the process above, with no success. It seems that if I am exporting and importing using the same delimited file into the same table in the same database, the import should work, doesn't it?!?
 
This may be your problem.
BUG #: 53386 (SQLBUG_70)

SYMPTOMS
========

When you use the "Copy table(s) from the source database" option of the Data
Transformation Services (DTS) Import wizard to transfer a table with a timestamp
column, DTS fails with the following error:

General error -2147217887 (80040E21). Errors occurred

CAUSE
=====

This error occurs if the destination table is also defined with a timestamp
column. The error occurs regardless of whether the transfer has the "Drop
destination objects first" or "Append data" option enabled.

WORKAROUND
==========

- Use DTS and specify "Use a query to specify the data to transfer". The query
should exclude the timestamp column.

-or-

- Use DTS and specify "Transfer objects and data between SQL Server 7.0
databases" and then specify which table you want to transfer.

-or-

- Define the destination table to use binary(8) for the datatype for the column
which will contain the timestamp.

STATUS
======

Microsoft has confirmed this to be a problem in SQL Server 7.0.
 
Try importing the data into the table but without the timestamp column, that should solve this issue. AL Almeida
NT/DB Admin
"May all those that come behind us, find us faithfull"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top