Hi - I have the following environment Windows Server: 2008 R2 Cluster: Yes - 2 Node SQL Server: 2008 R2 Enterprise SP2. I have SSIS package that has two data providers 1. Text (for input files) 2. Ado.NET for SQL Server destination. When I schedule and execute package from SQL Agent Job, the package fails with connection time out and max connections reached. sys.sysprocesses shows over 1000 connections and never closed or reused. As an alternative - Checked the 32-bit option during execution from the SQL Job and it makes very few connections, re-uses them and works fine. Can anybody help me out on this? ANOTHER Environment: Took the same package and deployed to workstation OS: WIN 7 SQL SERVER: 2012 Works just fine in 64 bit and has few connections, they are being reused and the performance is 10 times more on desktop environment ! Thanks for your help and input in advance

What if you replace the SQL Server Destination with an OLE DB destination. There about the same speed if you use the fast load option and OLE DB gives less issues.MCTS, MCITP - Please mark posts as answered where appropriate.

Koen - Thanks for your input. But still it doesn't solve the issue I have. I can try the workaround but its not a solution. Thanks again