dbTalk Databases Forums  

Connection pooling and transactions in DTS

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Connection pooling and transactions in DTS in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Sankar
 
Posts: n/a

Default Connection pooling and transactions in DTS - 07-11-2005 , 08:28 AM






Hi,

Has anybody made use of grouping together a set of tasks into a single
transaction in DTS? I suppose, by default, the transaction gets committed per
task. Is it advisable to use a single transaction for a group of tasks? In
what scenarios is this useful?

Is there any concept of Connection pooling in DTS? In what scenarios do we
need to make multiple connections?

Any pointers regarding this will be very helpful.

Regards,
Sankar


Reply With Quote
  #2  
Old   
frank chang
 
Posts: n/a

Default RE: Connection pooling and transactions in DTS - 07-11-2005 , 09:35 AM






Sankar, In a DTS package it is possible to join some or all of the tasks into
one transaction. If you check the Use Transactions options on the Advanced
tab of DTS Package Properties dialog, this option states that the DTS package
will support a transaction and you can configure the steps to join the
transaction. .... You can
configure a step's participation in a transaction on the Options tab of the
Workflow Properties dialog box by checking the join transaction if present.
The following tasks can participate in a DTS transaction,
Transform Data, Data Driven Query , Execute SQL Bulk Insert,
Message Queue, Execute Package.
The following tasks cannot participate in a DTS transaction,
Copy SQL server Objects, File Transfer Protocol, Dynamic
Properties, Active X Script, Execute Process, Send Mail.
Finally. please be aware that the Excel 2000 Worksheet , Access 2000
Tables and text file data sources do not support DTS Transactions.

"Sankar" wrote:

Quote:
Hi,

Has anybody made use of grouping together a set of tasks into a single
transaction in DTS? I suppose, by default, the transaction gets committed per
task. Is it advisable to use a single transaction for a group of tasks? In
what scenarios is this useful?

Is there any concept of Connection pooling in DTS? In what scenarios do we
need to make multiple connections?

Any pointers regarding this will be very helpful.

Regards,
Sankar


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.