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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-06-03 : 08:20:36
|
| Kitty Hundal writes "Hi,I'm running two DTS packages. One transfers data from BBX MKeyed files to SQL Server. The other updates SQL Server tables with the transferred data.These packages must execute consecutively. That is, the first transfer must complete, then the second package must execute. If I schedule these packages to run every minute separately, they run quickly (usually taking under a minute for both) using up to 100% of the CPU Processor, but only for a short period of time. However, since I don't know how long it will take for the first package to complete (depends on how much data is being transferred and could potentially take longer than a minute) it seems to be a bit risky to handle it this way. If I create another package which contains both of these packages and then schedule that package, for some reason, it takes a very long time for the package to complete execution. Up to 3 minutes on average.I'm now trying a third option. I've scheduled Package 1, then added Package 2 as step 2 in the schedule for Package 1. When step 1 completes, step 2 is executed, when step 2 completes, step 1 is executed.On my development box which has 1 CPU, this method hogs all of the resources. On our production box which has 2 CPUs, I'm hoping that only 50% of the resources will be used at any given time. I will be testing that this weekend, but need to have another option in the event that isn't the case. I'd really like to get some advice from you guys on this. Do you think my third option is reasonable and workable, if not, why, and what other options are available to me. I have training in database management, etc., but not specifically in SQL Server, so I've been figuring things out by trial and error.One suggestion made by the guys here was to create a step which was just a 60 second pause to free the CPU resources periodically. However, no-one knows how to do this. Any suggestions?Hopefully someone can give me an answer asap since I need to have this running by the end of the weekend.Terrific site, by the way. Tons of very helpful information for rookies like me :)Kitty" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
sql server and cpu processing 