I get the above error when I run a very simple DTS package to copy a
database from my production server to my development server. This has always
worked in the past. Unfortunately, it does not tell me which table is causing
the error (and 200 tables, so I don't want to run it for each one). Using the
database import/export wizard to do the copying gives the same problem.

I ran dbcc checkdb, but that reports no problems and did not help. Any
suggestions?

Thanks
--
Jan

This error has nothing to do with corruption, but just indicating that the
table structures are different between your prod and dev SQL Servers.

Can you run the DTS package interactively and see on which table you are
failing?

Or can you add a log file for the package and capture the output?

You could also use Profiler to see where your package is failing.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/



"Dutchieboy" <jang-donotspammme (AT) intertecservices (DOT) com> wrote

Hi Narayana , thanks for answering my post.

I did use a log file which gets the following:

Step Error Source: Microsoft SQL-DMO (ODBC SQLState: 21S01)
Step Error Description:[Microsoft][ODBC SQL Server Driver][SQL Server]Insert
Error: Column name or number of supplied values does not match table
definition.
Step Error code: 800400D5
Step Error Help File:SQLDMO80.hlp
Step Error Help Context ID:1131

So, that does not tell me where it is failing.

As for a mismatch between prod and dev, when I run the database import
wizard, I specify to drop the destination tables first - so how can there be
a mismatch?

As to running interactively, if you don't mean using the database wizard, I
don't know how to do that.


--
Jan


"Narayana Vyas Kondreddi" wrote:

The simple way is select the option to write the log file on dts only.

"Dutchieboy" wrote:

Sorry, I'm not a professional db admin. How do I do that?
--
Jan


"Gopalan" wrote: