00 A.M. WHAT SHOULD I DO

2:00 a.m. What should I do?

A: You could create two SSIS packages. One package would export from the

source system to an intermediate file (csv, or better yet use SSIS’s RAW file

format). Schedule that package to run at 10:00 p.m. The second package would

import from the intermediate file to the destination server. Schedule that

package to run at 2:00 a.m.

Q: I created a package in BIDS. The package ran successfully on my workstation.

When I deployed it to the production server, it failed. What could be the

problem?

A: When you run a package in BIDS on your workstation, it runs with your

credentials and uses data paths that are relative to your workstation. When you

deploy it to a production environment, it is normally being run with the SQL

Server Agent service. Ensure that the SQL Server Agent Job is being run with

a proxy that has access to the databases the package connects to, and that the

connection strings to the databases are correct for the production environment.

Q: I want to create a package that imports data daily from a text file that has a file

name based on the date and time the file was created. Can I do that with the

Import and Export Wizard?

A: Unfortunately, no. This is an example of where you would need to create

a custom package using BIDS. You could create the custom package using a

sample file with the Import and Export Wizard, but you would have to open

the package in BIDS to implement the dynamic file name and redeploy the

package.

Self Test