Smartssolutions

Wednesday, January 5, 2011

RetainSameConnection property

A situation could happen, if we are in situation where multiple tasks will use the same connection,  let's say a connection to a  given SQL Server instance data base. In fact, each task will use its proper connection even if the connection will hold the same  properties configuration. Once the task is executed the connection instance will be garbage collected and new connection with the same properties will be created for the next task. This would decrease the performance of the package execution. To avoid that we need to
1. Create one unique connection for the entire group of tasks
2. RetainSameConnection boolean property to true

Once the RetainSameConnection is set  to true then the connection will remain and will be used by the entires tasks group without having the necessity to recreate new connection for each task

No comments:

Post a Comment