Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
krn25
Starting Member
2 Posts |
 Posted - 2006-12-20 : 03:17:56
|
| Hi AllI'm hoping someone can help as this is driving me mad.I have a number of sql server 2000 DTS packages (20) which i have moved to a new server. All work perfectly on this server when scheduled.I have nested these packages into 4 master packagese.g. master package A contains packages 1 to 5etcAll these master packages work perfectly on the server when scheduled.I have further nested the packages into one overall package.Within this A should start B on completion, B should start C on completion and C should start D on completion.When i run this A and B will complete but package C does not run.As far as i can see B completes and suceeds. I have even put a sql task on the end of B to see if it suceeds - and it does. But i can not get package C to run after A and B.I can get B then C to run if A is missed out.This overall package runs on the development server - why won't it on the production server.I can see no reason for this. Error and package logging does not show any problems.I am completely stuck. I dont want to schedule them separately as some need to complete before others. I dont want to put all 20 into 1 package as, in time, others will be added in the chain, so splitting will make maintenance easier.Suggestions pleasekrn.krn25 |
|
|
readysetstop
Posting Yak Master
123 Posts |
Posted - 2006-12-28 : 09:15:54
|
| krn25, Why are you using that many levels of nested packages? Seems like too many moving parts to me. What's the goal here?Are you logging execution of all the packages, or just the ones that trigger other packages? Are the triggered packages being logged as well? Have you done a trace?-d. |
 |
|
|
|
|
|
dts package not triggering next dts package