DTS ROADMAP

UNDERSTANDING PACKAGE

• Does the package import or export data?

• What step raises error and what is the exact error?
• What is the source and destination?
o If they are using files where are they located and are they referenced using
unc?
o If there databases servers used, do the connection object use ODBC or
OLE DB to connect? What version and vendor provides the drivers? Can
Microsoft providers or drivers by used?
• What transformations occur when data is imported/exported?
• If SQL Server is the source or destination does the connection object use sql or nt
authentication?
• Does the package access resources on other servers?

UNDERSTANDING PACKAGE EXECUTION

IDENTITY WHEN AND HOW PACKAGE IS EXECUTED

FROM ENTPERISE MANAGER

• If a package can be run from Enterprise Manager is the customer using Enterprise
Manager on the server itself or from their workstation? When run on a workstation, the
package actually executes on the workstation even if the package is stored on a server.
• If they are using Enterprise Manager on a client, can you execute the package using
Enterprise manager on the server itself?
• Can the package be run using Enterprise Manager from another client?
• If you are running from Enterprise Manager, what account are you logged in with?

From an application using DTS OBJECT MODEL

• Is the package being run from an application, ex Visual Basic? If so where does the
application reside.
• If the package is initiated by an application, how is the application invoked? What account
is used to start the application?
• The package will run on the machine used to invoke the application.

AS A SQLAGENT SCHEDULED JOB

• If the package fails as a scheduled job, who owns the job? Is the job owner a system
administrator in SQL Server?
• If the package fails as a scheduled job and the job is owned by a system administrator in
SQL Server, what is the startup account for the SQL Agent account?
• If the package is owned by a non-system administrator what is the SQL Agent proxy
account set to?
• Do other jobs owned by the same account work? You can setup a test TSQL job to see if
that can be run.
• Do other cmdexec (os) jobs work?
• Can the package be run using the dtsrun.exe from a command line while logged in with
the same job owner?

DATA TO COLLECT

• Exact error message, number, and source:

o If the package fails from Enterprise Manager, double click on the
failed step and see if a more detailed error message is displayed.
o Configure DTS package log and send in log file
o Try running dtsrun.exe from a command prompt and redirecting output
to a file.
• If SQL Server is involved, check SQL Server error logs.
• NT System and application event logs.
• Version of SQL Server and version of tools used to execute the package if the
package is run from a client
• MDAC Version of where package runs.
• If you are unsure exactly what the package is doing, have the customer save
the package to a structured storage file (.dts) and send that in.