I have an SSIS package and have been adding additional DFTs to it. Where there are dependencies between transformations I identify them. However where things can procceed in parallel I do not constrain them form a control flow standpoint.
After adding another DFT I am now getting package failure due to "Database server connection limit exceeded" (my local source database is SQL Anywhere and it has a max connections of 10 in production it will be full blown Sybase and will probably
not be so constrained). I think I can solve the problem just my making control flow dependencies to reduce the amount of parallel activity but I am wondering if there are other things I should consider doing. For instance are there other settings
I can tweak that tell SSIS to run parallel up to X connections out of a connection pool? (or something like that).
Some may comment that this relates to my post of yesterday on package strategy (master-child packages or one big package). I still have one big package for now but may break it into master-child. Still I think I can control the amount of parallel
activities through control flow even if it remains one package.
Any thoughts or comments on this would be appreciated.
PS - just ran my package and this time it succeeded - sometimes I hit the limit of 10 connections sometimes not...
View Complete Post