DTS Packages in SQL 2005 - what are they now, etc

OK - so it looks like DTS Packages are "legacy". I installed the component to be able to edit and run them from SQL 2005 Management console and that seems to work fine. (I haven't acually run my packages yet, but at least I can open and edit the dang things). And I also migrated the existing ones from the networked server on which they lived (which is still running SQL 2000) to my local server (which is the one on 2005).

So assuming I want to do the new methodology - what IS the new methodology?

Where are the migrated packages? I looked at all of the links in the SQL Management Console for anything that references these newly migrate packages, and I don't see them - or anything that looks like them - anywhere.

What do I run them in - from what, how, etc? This really isn't clear at all.OK - so I think I have this figured out. You have to connect to Integration Services for a specific server. If you do that, they are then in the Stored Packages. So I'll post back if I have any problems when I actually get up the courage to try and run these puppies...|||That's correct. If you used the destination as a server, you have to connect to Integration Services and then see the packages under MSDB in stored packages. Alternatively, you can choose "DTSX File" as the destination for your migrated packages, and then save your packages as .dtsx files in your chosen folder. You can then add these packages to an SSIS Project and view/edit them in BI Studio.|||Hi.
Yeah, they are unregular XML-files, I guess. Not to be edited.

Try to enable and start the "DTS Server" service, then run
cmd
dtexec.exe /?

They can also be scheduled from within managment studio and run from bi studio.

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (
to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
John
there is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>
|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one?
"Jéjé" wrote:

> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>
>

DTS packages in SQL 2005

I see them show up under a node called Legacy in Management Studio. What is
the plan for migration of DTS packages from 2000 to 2005? We have lots of
these that we'll need to migrate that are in use with various SQL jobs.
Thanks,
Johnthere is a migration wizard to help you.
but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
make sure that the upgrade is correct and to use the new features)
but you can continue to execute your DTS packages in 2005.
"John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
>I see them show up under a node called Legacy in Management Studio. What is
>the plan for migration of DTS packages from 2000 to 2005? We have lots of
>these that we'll need to migrate that are in use with various SQL jobs.
> Thanks,
> John
>|||Have you found any documentation about what kind of code or task need manual
job to be migrated? Or should I learn it on the field, one by one'
"Jéjé" wrote:
> there is a migration wizard to help you.
> but you'll have a lot of manual job to do to really convert DTS to SSIS. (to
> make sure that the upgrade is correct and to use the new features)
> but you can continue to execute your DTS packages in 2005.
> "John Holmes" <johnsh@.co.skagit.wa.us> wrote in message
> news:efrhJH5IGHA.140@.TK2MSFTNGP12.phx.gbl...
> >I see them show up under a node called Legacy in Management Studio. What is
> >the plan for migration of DTS packages from 2000 to 2005? We have lots of
> >these that we'll need to migrate that are in use with various SQL jobs.
> >
> > Thanks,
> >
> > John
> >
>
>

DTS migration wizard, where does it put migrated version?

From SQL Server Management Studio I right click on Management/Legacy/DTS and select Migration Wizard and enter a SQL Server Source and Destination. A list of DTS packages from the source server is displayed and I select one of the DTS packages and give the destination a unique name. The wizard runs and says it's successful. I can't find the new SSIS version of the DTS package with the new name that I've given it, however. Where does it put the new migrated copy of the DTS package.

Thanks,

John

In Sql Management Studio, under the Object Explorer window in the Connect drop down choose Integration Services, and it will show you all stored packages on that instance.|||Thanks, this helps. Now I'd like to find out how to edit the migrated version. How to I get to it from BI Dev Studio?|||

All of the stored packages will usually be in ~\Program Files\Microsoft SQL Server\90\DTS\Packages

DTS Legacy and SQL 2005

I am in the process of migrating to a new SQL 2005 server. I have a number of DTS packages on my SQL2000 server, approximately 200, that are used on a daily basis. I used the migration wizard to migrate the packages from the 2000 server to the new 2005 server however there are issues with the way some were brought over. I would like to have all of the packages moved from the 2000 to the 2005 server and appear under Legacy DTS so that I can run them as 2000 DTS packages unitl I have a chance to correct the issues.

Here is where my question lies. The migration wizard migrates upgrades all of the packages. How do I move them from the one server to the other and perserve their 2000 DTS format? The servers are on 2 separate boxes with different instance names. Everything I've read tells you how to run the legacy packages but nothing seems to explain on to move them.

Any help would be appreciated

Pete

As you have found the migration wizard attempts to create new SSIS 2005 packages from your DTS packages. Due to the fundamentally different architecture this can be limited in its success.

Moving your DTS 2000 packages to a new server, should be effectively the same as moving DTS packages between 2000 servers, so the following information may still be valid: http://www.sqldts.com/default.aspx?204

However, note that I have not tested this scenario - it is only a suggestion and would need some testing and experimentation.

Donald

|||

Maybe not very polite, but what the heck! why you want migrate them to Sql25k instead of make them from the beginning taking advantatge of all that native stuff?

We've got around 500 and most of them on-daily basis. We have come to the conclusion that left the old ones inside a rubbish.

|||

Although, of course we're talking about bank sector...Thing going here slower

I suppose that if you have mainly DTS packages with the usual tasks (pumping, sql tasks, vbScript and nothing else) migration could be successful from Sql25k otherwise if you have DTS with custom tasks it might not easier.