Ian,

I will try to answer inline.

I personally keep DTS packages stored in Structured File Storage for a
number of reasons. So I would just copy them out and put them in the proper
folder. From SSMS you can export packages from a server, one at a time, to
files. Then, if you like keeping them in msdb you can import the files, one
at a time.

If they were scheduled on your original server, there are SQL Agent jobs to
cause those schedules to execute. Script those jobs using SSMS and then use
the scripts to recreate your 2005 server's jobs. You may need to make
changes depending on where you keep your packages, what logins exist on the
new server, etc.

Since I wanted the same basic server settings for everything I keep in msdb
and master here is what I did.
1. Install fresh server with SQL Server 2005, then shut down the SQL
services.
2. Copied the detached database files from the old server to the new server.
Be sure that msdb (and master, if you choose that) files overwrite the
freshly installed msdb mdf and ldf.
3. Restart the server, which upgrades msdb to 2005, and keeps all my
packages, job definitions, etc.
(If you also copied master you keep your logins as well.)

No, as noted below the DTS package is independent of the SQL Agent job that
runs it. (It may not look that way when you schedule the job from DTS, but
they are independent objects.)

I don't have an answer for this question. Sorry.

RLF

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote:

In SQL Server Management Studio, open the instance of SQL Server in which you
want to create a job, or the instance that contains the job to which you want
to add a step.

Expand SQL Server Agent and do one of the following:

To create a new job, right-click Jobs and then click New.


To use an existing job, expand Jobs, right-click the job, and then click
Properties.


On the General page, if you are creating a new job, provide a job name,
select an owner and job category, and, optionally, provide a job description.

To make the job available for scheduling, select Enabled.

Click Steps, and then click New.

Provide a step name and, in the Type list, select SQL Server Integration
Services Package.

In the Run as list, select the proxy account with the credentials that the
job will use. For more information, see the following topics:





"Russell Fields" wrote: