DTS Package Development, Deployment and Performance
On This Page
[pic]SUMMARY
[pic]MORE INFORMATION
[pic]Making Data Connections Flexible
[pic]Controlling Packages with Global Variables
[pic]Passing Parameters to a DTS Package
[pic]Writing Custom DTS Tasks in Visual Basic
[pic]Obtaining Information on How to Code DTS Packages
[pic]Enhancing DTS Package Performance
[pic]Using Parallel Loads
[pic]Insert Commit Size
[pic]DTS and Distributed Transactions
[pic]Error Message
SUMMARY
The purpose of this article is to provide some detailed information to assist in the development and deployment of SQL Server 7.0 Data Transformation Services (DTS) packages. Hints for improving package performance are also provided.
For information on this subject in SQL Server 2000, see SQL Server Books Online.
MORE INFORMATION
Making Data Connections Flexible
A DTS package is a completely self contained unit. All connection information is read into the connection properties collection at design time, even connection information in UDLs and ODBC DSNs. If you change the ODBC DSN or the OLEDB UDL after creating the package, that change has no effect on the package. This is important to remember when trying to migrate packages from a development environment to production.
When you use SQL Server data connections, use (Local) for the server name to make it easier to move the package from server to server since the name of the server is resolved at package execution time. The one caveat to this approach is that it requires that the package be run and edited on the SQL Server computer itself.
You can also use an ActiveX script task or a wrapper program to modify package properties at run-time. To modify the package ...