SSIS Execute Package File Connection Help

Hello all,

Hoping this is simple.   I have an SSIS package that I need to deploy to a batch server.   I found a sample one that I am using and modified.   I have a Master package master.dtsx and in that package I am writing to a log then running multiple other packages then logging completed in the master package.   So I have three Execute Package Task Editors that use three connections in the connection manager that are the other packages.   The sample I have has a variable in the master package called "BasePath" that I have been filling out with my C: drive path to the solution.   All these packages are under the same folder.   In the master package code it shows for example:


<DTS:Property DTS:Name="CreationName">FILE</DTS:Property><DTS:PropertyExpression DTS:Name="ConnectionString">@[BasePath] + "CDCCashflow.dtsx"</DTS:PropertyExpression>

Stupid question is can I just have it look in the same root path for the files instead of having to enter in a base path to get it to run?   This way I don't have to enter in a hard path.
sbornstein2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Phillip BurtonDirector, Practice Manager and Computing ConsultantCommented:
You can use a parameter instead of a variable, and even have a default value for the parameter for use at design time.

See this web page for more information: http://msdn.microsoft.com/en-us/library/hh213296.aspx 

This way, you can pass the parameter into the expression rather than having to use a hard path.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DcpKingCommented:
Phillip is correct. In addition, you could also consider keeping your paths in a table and populating the values at runtime using the Execute SQL task (see Microsoft docs here). This approach would allow you to change locations in the future without changing the packages.

Once you do that, of course, you can extend the concept logically by keeping a list of the packages you want to run in a table, and have your Master package read the table to  see what other packages to run, rather than hardcoding the package naes, etc., into the Master ...

Have fun!

hth

Mike
0
sbornstein2Author Commented:
thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.