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 |
|
nr
SQLTeam MVY
12543 Posts |
 Posted - 2003-12-17 : 06:28:57
|
| Just arrived at a site which uses dts to control everything (yuk).They set the connections via a dynamic properties task from an ini file.They say that this sometimes continues before setting the connections and so they include a 5 second wait as the next step.I have my doubts about this because in a lot of packages they have included database processing before the wait step.Everything is very simple with on success workflow connecting a single thread.Has anyone come across this before?==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
VyasKN
SQL Server MVP & SQLTeam MVY
313 Posts |
Posted - 2003-12-17 : 08:12:54
|
| What I've seen is that, many people leave the 'Dynamic properties' task hanging in the package, without linking it to the workflow. That's when we see that problem. Yes, simply make the 'Dynamic properties' task the first step to run, and the rest of the steps run 'on success' of this step. This solves the problem.--HTH,Vyashttp://vyaskn.tripod.com |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2003-12-17 : 08:29:51
|
| Everything is linked in a single thread with two dynamic properties tasks at the start. One to set the servers then one to set the databases.I have a strong syuspicion that they had another problem and thought this fixed it.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Dynamic properties delay