Home > Articles > Data > SQL Server

The DTS Object Model

This second article in the three-part DTS series by Baya Pavliashvili and Dan Lampkin introduces you to the main objects and properties of the DTS object model, with a concentration on the major properties that you’ll need to set in almost every package.
Like this article? We recommend

In this second article of the DTS series, we introduce you to the main objects of the DTS Object Model and their properties. We will delve into each major object and show the code for a simple yet complete DTS Package. There are numerous properties you can set for each DTS object, and discussing each of them in detail isn't feasible for this article. Instead, we concentrate on the major properties that you'll need to set in almost every package. Please refer to Microsoft SQL Server Books On Line (BOL) for additional information.

Many DTS Packages can be designed using the DTS designer and executed in the same manner every time. But if any of the details are not known at design time, it may be easier to design a package that can obtain needed pieces of information at runtime.

Many DTS Packages will be built directly in Visual Basic (VB) code. The VB component can create a package that will transfer and transform the data. This way, you can store information in a database or pass it to a VB component at runtime. Storing the information in the database allows you to set different parameters within each database, and use the same component to build and run the package.

As we build the sample package for this article, you can follow along if you want by building your own package. You can download all of the code as well. If you will build one from scratch, you must add the following references in your VB project: Microsoft DTSPackage Object Library, Microsoft DTS Custom Tasks Object Library, and Microsoft DTSDataPump Scripting Object Library. Your package may not need the last two, depending on your package, but we show all of them for your convenience.

Package2 Object

The topmost object in the DTS object model is the Package2 object. All other DTS objects are related to the Package object. For example, if you add a connection to SQL server, the Connection object must be told that it is a part of a specific package. So let's start by examining the Package object more closely.

Many parameters of the Package2 object will remain the same from one run to the next on a specific system, so we can hard-code properties that are not likely to change. The PackagePriorityClass property sets the thread priority for the package in the operating system. Microsoft has provided three constants that can be used to set the value of this property: DTSPackagePriorityClass_High, DTSPackagePriorityClass_Low, and DTSPackagePriorityClass_Normal. If you have packages that you want to run at different priorities, then you can add the logic in the code to set priorities accordingly; otherwise, we can just hard code the setting as follows:

.PackagePriorityClass = DTSPriorityClass_Normal

Data lineage is used to track meta data about the objects used in the package. You can use the LineageOptions property to tell how the data lineage will be written. Again you have several constants to choose from: DTSLineage_AddLineageVariables, DTSLineage_None (default), DTSLineage_WriteToReposIfAvailable, and DTSLineage_WriteToReposRequired.

Look for "data lineage" in the index of (BOL) for more information about using data lineage. In our example, we hard-code this value: LineageOptions = DTSLineage_None. The TransactionIsolationLevel is used to set the isolation level if the UseTransaction property is set to true. We have the four standard SQL Server Isolation Levels, plus we get several additional ones to choose from for non-SQL Server databases (see Table 1 for the available constants). Set yours to whatever meets your needs for your specific package.

We set ours like this:

.TransactionIsolationLevel = DTSIsoLevel_ReadUncommitted

We chose the ReadUncommited level because we're only exporting data to a file in our example.

Table 1 DTS Transaction Isolation Level Constants




Prevents dirty reads and allows phantom reads.


No shared locks are issued; exclusive locks are ignored. Least restrictive.


All data is locked, but allows inserts by other users.


Prevents all other user access, insert, update, or delete. Most restrictive.


Similar to ReadUncommitted; not for SQL Server.


You can see uncommitted changes by other users, but update locks are not held to the end of the transaction. Rollbacks are not allowed. Not for SQL Server.


Locks a single row of data as rows are FETCHed using a browse cursor.


Similar to Serializable. Not for SQL Server.

The RepositoryMetadataOptions property has to do with scanning database objects into meta data services. We don't need to adjust it for this example because we don't intend to store meta data about the sample package, so set it to the default:

.RepositoryMetadataOptions = DTSReposMetadata_Default 

We also have several constants that we can choose for this property.

In SQL Server 2000, we have two kinds of authentication: Windows and SQL Server security. We indicate the type of authentication we are using with the LogServerFlags property. This property sets or returns the kind of authentication to be used for a package. We'll use the SQL Server authentication and set it in the following manner:

.LogServerFlags = DTSSQLStgFlag_Default

If you want to use Windows authentication, use the DTSSQLStgFlag_UseTrustedConnection constant. Because there are several ways that a DTS package can be created, we have a property that lets us specify how the package was created. The PackageType property indicates how the DTS package was created; we'll set ours to .PackageType = DTSPkgType_Default to indicate that it was a custom package.

The MaxConcurrentSteps property can be used to tell the package how many steps may be ran simultaneously. If the system has only one CPU, then setting this value higher than one has no effect. Set this value to a value up to the number of CPUs on the system that the package will run on. If the package will run on different computers, then having this value set higher than the number of processors has no effect, so you can set it up to the number of processors on the computer that has the most processors.

BOL has information on all of the properties we use, and much more. It also contains a list of all the predefined constants that are available for each property. You can also see the available properties through your intellisense in VB. To find the properties in the BOL, review the Package and Package2 objects.

If you see an object with a 2 on the end, it just means that it is a DTS 2000 object and cannot be used in earlier DTS versions.

We can create a method to set these values, and pass in any of the values that change during each execution of the package. Most of these values will remain the same for a particular system, so many of them can be set at design time. Also, the Description property is not needed, but I like to give a short description, so that if I save the package, I can read that description for all of the packages at once from the Local Packages section within Enterprise Manager. Actually, we can make many of the object creation processes general enough to put them into a method, which saves us from writing out all of the properties each time we want to create a new object. It also allows our objects to be consistent in how they are created.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020