Showing posts with label upgraded. Show all posts
Showing posts with label upgraded. Show all posts

Thursday, March 22, 2012

DTS packages not migrating completely

Hi, I upgraded several of my SQL 2000 database to SQL 2005 databases. I'm in the process of migrating over the DTS packages over to SSIS packages. I'm using the DTSMigrationWizard utilty to do this migration. When I started testing the SSIS packages I've discovered that not all the steps were being excuted. So I've noticed on several of the packages not everything migrated over. Such as connections to oracle and some of the task as well did not migrate over. Is there a way to migrate the entire DTS package to SSIS or do I have to re-create the entire package from scratch or is there a better way to get the SQL 2000 DTS packages over to SQL 2005 and have them run successfully?

You can have the SQL 2000 DTS packages in a SQL 2005 server and still keep running them (using the DTS runtime). If you chose to migrate, please be aware its a best-efforts migration as DTS and SSIS are different products. See http://technet.microsoft.com/en-us/library/ms143462.aspx for more details on known issues during migration.

DTS packages not migrating completely

Hi, I upgraded several of my SQL 2000 database to SQL 2005 databases. I'm in the process of migrating over the DTS packages over to SSIS packages. I'm using the DTSMigrationWizard utilty to do this migration. When I started testing the SSIS packages I've discovered that not all the steps were being excuted. So I've noticed on several of the packages not everything migrated over. Such as connections to oracle and some of the task as well did not migrate over. Is there a way to migrate the entire DTS package to SSIS or do I have to re-create the entire package from scratch or is there a better way to get the SQL 2000 DTS packages over to SQL 2005 and have them run successfully?

You can have the SQL 2000 DTS packages in a SQL 2005 server and still keep running them (using the DTS runtime). If you chose to migrate, please be aware its a best-efforts migration as DTS and SSIS are different products. See http://technet.microsoft.com/en-us/library/ms143462.aspx for more details on known issues during migration.sqlsql

DTS packages and SQL 2005 upgrade/issues

Case one - upgrade from SQL 2000 to SQL 2005 in the same box

(actually it is a copy of the test box being upgraded)

Case two - install fresh SQL 2005 in a different box

Results for running (dts packages migrated to dtsx) in SSIS from a job

Note all other jobs in (Case one) using the old DTSRUN works fine, but new jobs trying to run migrated packages fail. Migrating this new package to (Case two) runs. How do I troubleshoot this? The process exit code was -532459699.

Is this exit code something that can be looked up?

Case one
Date 4/17/2007 2:51:49 PM
Log Job History (TEST SSIS5)

Step ID 1
Server USXXXX4O
Job Name TEST SSIS5
Step Name SSIS5
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: xxxx. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:51:49 PM. The return value was unknown. The process exit code was -532459699. The step failed.


Case two
Date 4/17/2007 2:34:07 PM
Log Job History (TEST SSIS5)

Step ID 1
Server USXXXX4
Job Name TEST SSIS5
Step Name SSIS5
Duration 00:00:07
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: xxxx. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:34:07 PM DTExec: The package execution returned DTSER_SUCCESS (0). Started: 2:34:07 PM Finished: 2:34:14 PM Elapsed: 6.328 seconds. The package executed successfully. The step succeeded.

You should set up logging to get more descriptive messages.

Have you run the package manually to see if it gives different results or where it fails?
|||

Manually runs fine for both cases from within SQL Server BI Dev Studio and also the SQL Server Mmgt Studio.

Got a link to the logging setting you mentioned earlier.

Thanks.

Sunday, February 26, 2012

DTS Migration Wizard question

Hi,
I've upgraded from 2000 to 2005, 2005 on a new server too.
I have moved a DTS package from the 2000 box to 2005 box & have performed th
DTS Migration Wizard.
Now I want to fiddle with the design of the package in Business Intelligence
Design Studio. Where the heck is it (the migrated package)? How do I open
the package in this wierd GUI?
cheersTry to connect to Integration Services and expand "Storage Packages", just t
o
see where you saved your package.
To edit the package, run Business Intelligence Development Studio, create a
new Project (using Integration Services Template) and in the new Solution ad
d
an existing package; following the dialog boxes you should navigate to the
path where your package is stored.
Gilberto Zampatti
"dc" wrote:

> Hi,
> I've upgraded from 2000 to 2005, 2005 on a new server too.
> I have moved a DTS package from the 2000 box to 2005 box & have performed
th
> DTS Migration Wizard.
> Now I want to fiddle with the design of the package in Business Intelligen
ce
> Design Studio. Where the heck is it (the migrated package)? How do I ope
n
> the package in this wierd GUI?
> cheers
>
>

DTS Migration Wizard question

Hi,
I've upgraded from 2000 to 2005, 2005 on a new server too.
I have moved a DTS package from the 2000 box to 2005 box & have performed th
DTS Migration Wizard.
Now I want to fiddle with the design of the package in Business Intelligence
Design Studio. Where the heck is it (the migrated package)? How do I open
the package in this wierd GUI?
cheersTry to connect to Integration Services and expand "Storage Packages", just to
see where you saved your package.
To edit the package, run Business Intelligence Development Studio, create a
new Project (using Integration Services Template) and in the new Solution add
an existing package; following the dialog boxes you should navigate to the
path where your package is stored.
Gilberto Zampatti
"dc" wrote:
> Hi,
> I've upgraded from 2000 to 2005, 2005 on a new server too.
> I have moved a DTS package from the 2000 box to 2005 box & have performed th
> DTS Migration Wizard.
> Now I want to fiddle with the design of the package in Business Intelligence
> Design Studio. Where the heck is it (the migrated package)? How do I open
> the package in this wierd GUI?
> cheers
>
>