Could someone give me some pointers please
I'm developing a data warehouse project.
What is the best practice for calling subsequent packages? I know that it's best to compartmentalise the process into logical work - ie. update a dimension etc, but I'm a little lost as how this is best done, when it comes to deployment.
I've developed a LoadDimensions package that executes other packages - such as LoadCustDim, LoadProdDim etc etc.
what I have found when defining the package to execute though is
1) if I use File System, and refer to my local project copy, then when it's deployed, it will refer to that source package copy, not the deployed copy - which is what I want it to do.
2) if I want to reference the packages in the deployed environment, stored in the msdb, then I have to first deploy the LoadCustDim, LoadProdDim etc etc, and then I can deploy the LoadDimension package.
My question is, can I configure the package reference to be relative, to the local calling package??
I'm going to be moving across to SQL2005 and SSIS very soon now, so I would really appreciate some help and advice on how this is tackled with a live and development environment. I'd like to hear how other people handle this as to me, it all seems a little disjointed and clumsy.
MCITP: Business Intelligence Developer (2005)