March 5, 2008 at 1:41 pm
On production, our SQLServer 9.0.2050 legacy dts packages are delayed, slow to load by scheduled jobs. This is not occurring in development or staging. This has not occurred before.
In another symptom, using SMSS on the production server, Management | Legacy | Data Transformation Services, when selecting a dts package and ‘open’ from the menu to use the dts designer, any dts will not load or display for several minutes. Once displayed, all dts packages will open immediately. When using SMSS from my workstation, I don’t experience this delay.
We restarted SQL Server Agent, and SQL Server with no impact. We are considering rebooting the server. The server appears to have adequate resources and does not seem stressed. We cannot think of any strategic changes recently made.
Any insight or suggestions to return to the immediate opening of dts to display, or to immediately run by jobs?
March 5, 2008 at 1:45 pm
That's an odd one and I'd really like to hear more on this as I've been using DTS in 2005 quite regurarly without any problem. The fact that loading the DTS package via SSMS and not even running is taking long, is quite odd ...
I'd start with a trace, targeted at your login only and then see what is being run when you are opening up the DTS and compare that to your DEV/QA environment.
Also, for S&G's, I'd check the index fragmentation on the msdb system dts tables (sysdtspackages,sysdtspackagelog,sysdtssteplog).
March 11, 2008 at 12:57 pm
Adam, et.al.,
Sorry for the late get back. Finally, on the weekend, we rebooted the server, which took care of the anomaly. "Wipe on, Wipe off". So many issues are managed by starting over, backing out, reinitializing.
I'm guessing this was some memory/cache issue, though I wouldn't quite know where to start to confirm that. And again, it's easier to fix something than know the 'why'. Thanks for your input
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply