Sunday, February 26, 2012

DTS Migration to SSIS

Good Day,

I am currently in the process of migrating my DTS packages to SSISone at a timeand have come accross the following error during the excecution of a "Copy SQL Server Objects Task". The exact error is:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Version80 database compatibility level is not supported.".

What I am doing with this particular task is to copy a table(s) from another SQL Server, to the current SQL Server. The original location is a SQL2000 DB table. In the near future the source server for this table will be a SQL 2005 server but not until the current migration has been completed.

I have looked at all of the properties, but can not find anything relating to the db compatibilty level. Is there an easier way? Or a setting that I can change to accomplish what I am trying?

Thanks for any help/suggestions.

I have the same error . I'm copying from SQL 2005 to SQL 2005, and selecting all tables. Also having it copy all indexes, triggers, etc. Sometimes I can actually get it to execute successfully, however; there are no tables that have been copied when this happens. I'm betting this is another bug.

Really need this problem resolved since there already is a bug that have been recently report using the Transfer Database Object. Especially if we need to move a SQL 2005 database back to 2000, which my the situation in a case for me the other day. The only way was to export all the tables and then go back into the 2000 db and re-create the indexes, and relationships - not good.

We need the SSIS tools working correctly - DBA's rely on them!.

Hoping for quick resolutions.

Update: There is a solution. Check the Properties\Options of the database and look at the compatibility level. Most likely it is set to 8.0 as was mine. Change to 9.0 and it should now run. - Unfortunately when I ran mine, it led me to believe that everthing ran fine, but when I looked at the database, no user tables, etc. were there.

|||Try changing the provider to Microsoft OLE DB Provider for SQL server. The default provider probably does not work for SQL server 2000.

No comments:

Post a Comment