0

I have one master package and 29 child packages. I execute these 29 child packages from parent master package using an Execute Package task inside a for each loop container dynamically.

My concern is how can I deploy them in live? Should I create 29+1 database connection string with 30 configuration file because each child package executes a SQL Server stored procedure.

Any kind of suggestion is highly appreciated . Thanks

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Anil
  • 136
  • 1
  • 12
  • If they're all going to use the same database, why wouldn't you have them all use the same connection string in the same config file? – Tab Alleman Feb 17 '15 at 20:53
  • 29 child including master package will point to the same database – Anil Feb 17 '15 at 21:02

1 Answers1

1

I've had a similar challenge about a year ago. I've choosen to go for using a script task like it's described over here. A SQL Server Agent job passes in the connectionstring and variables (i.e. source file paths) to the master package, the master package can use this technique to pass those along to the sub packages.

MWillemse
  • 960
  • 5
  • 9