asked on

Saving a DTS package so it can be used on a different server

I am creating a database in SQLServer and will be scripting it up into a .sql file to send to my customer. They will run the script to create a copy of the database. Once the database is created (with empty tables), they will have to populate the database using data in an existing database on the same SQLServer. I would like to create the DTS package they will need to use (I have a copy of their database as well) and then send them the DTS package along with the .sql script. When I create the package using the DTS Wizard I see that I can save it in four different ways - I have only ever saved them as a Local Package on the SQLServer itself, so I don't know which of the other ways might work for what I need. The other ways are: SQL Server Meta Data Services, Structured Storage File, Visual Basic File.

Or maybe there's some way to "script" the DTS package once it's created as a Local Package? But that's just dreaming on my part. Can someone explain how I can do what I want? If this isn't clear I'd be happy to explain further.

Thank you!

SOLUTION

robertjbarker

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

robertjbarker

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rsoble

ASKER

Thank you, that is helpful. What is the difference between a Structured Storage File and a Visual Basic File? I mean in terms of how my customer will use it. Can they run it with the Query Analyzer just like they would a .sql file?

rsoble

ASKER

Ah. :) Gotcha.

Let me just test it out and then I'll come back and close the question.

SOLUTION

arbert

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rsoble

ASKER

That worked marvelously! When I did Open Package, I then had to save it as a SQL Server package and then it appeared back in my Local Packages right where I wanted it. I knew there was a way, so much faster to ask you smart people... ;)