Multiple Packages VS One Large Package 1

[sabloomer]

I am fairly new user of SQL Server 7.0. I has hoping that someone might be able to give me some insight into a question I have had. I am establishing a nightly process to import and groom my data that has over 20 steps. While I was testing the different steps I set up a DTS Package for each step. When it is time to runn all of them, would it be better to combine all of these into one larger package or would the best way to deal with it be to schedule the first package and then add the needed steps to the schedule? If the second idea is better is there an easier way to reference the package in a schedule? Right now the step reads "DTSRun /" followed and a long string of numbers and letters that do not mean anything to me.

Thank you for your time,

sabloomer

 

[JayKusch]

I would, IMHO, create all the steps in one package. You then will have to deal with just one package when it comes to debugging.

An added plus is that you can set alerting easier on each step within the package and then have appropriate emails sent out, execution halted, steps re-tried and a host of other tasks you need to do within the package. Remember, you have a 3 WorkFlows that you can use w/in your package to make sure the process accomplishes the needed steps.

You will also be reducing the resource overhead of starting multiple packages as oppose to just one or maybe 2 DTS packages.

Thanks

J. Kusch

 

[sabloomer]

Thank You. I am trying to teach myself and I was sure that there was a "right" way and things I was not considering. I am going to start bring the steps into one package.

sabloomer