October 17, 2006 at 6:05 am
Over the weekend we moved our database to a different server, first time I have done this. The old and the new servers both run Window 2003 and the same version of SQL (2000). I used a DTS package to transfer all of the DTS Packages over to the new server and all seem to be working well except for 2 of them. If I manually start the jobs they run as expected but if they run due to be scheduled they take as long as 3x what they normally had. We have looked at both DTS packages and compared them to what was on the old server and they are identical as far as we can tell. The only difference between the old and the new servers is that the old one was a stand alone server and the new one is on a SAN. We have look at permission's and security and anything else we could but not luck. I sure we are missing something really simple. Any Ideas???
Kurt Kracaw
October 18, 2006 at 12:56 am
Hi
I noticed you have said the same version of SQL have you checked the service packs on both servers and both SQL installations?
Mike
October 18, 2006 at 5:14 am
SP3 on the original server and SP4 on the new one. SP4 due to a financial software that is on this server. Could this be part of the problem? I can add a little more info now On the old server when the data pump was going you would see a noticable difference in performance on the new server it is less noticable. When ever we try something/anything new the performance gets better for one run and then returns to longer runs. If any more info is needed please let me know asnd I will get back to you as soon as possible.
Kurt Kracaw
October 18, 2006 at 12:36 pm
You say you have two packages that run three times slower as a scheduled job than they do when you run them manually (even though other packages don't seem to have any performance issues).
One difference may be the computer the DTS process is running on. When running as a scheduled job the package executes on the server, but when you open and run the package in Enterprise Manager it runs on your workstation. Usually running a package on a server (which is used as a connection in the package) is faster because network traffic is reduced, but conceivably there are network configurations where your workstation has a faster connection to something (different switches, fewer hops, etc.).
Another difference may be timing. Are you comparing the manual job run during working hours to a scheduled job running in the middle of the night? Theoretically jobs will run faster during off-peak hours, but in reality they may be competing with a backup or some other scheduled activity.
Sorry I can't be more helpful, but there isn't much to go on. I think you need to focus on why these two packages are different than the others, and why they run differently manually vs scheduled (different login, different host computer, different time of day).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply