August 17, 2009 at 9:23 am
I have a very peculiar issue going on. We have a job that runs at 3:30am. Sometimes, the DTS package will appear like it's hanging, but it's actually loading data very slowly. SQL Server appears idle. It's almost as if its trying to load data on a 56k modem. Network utilization is very low. My theory is that SQL Server doesn't seem to update it's network speed if there is a problem. I've noticed this on backups as well (only on 2000, 2005 seems to well). Normally, this job takes 40 minutes to run. I found it today in it's second day of loading data at a snails pace.
When I change it to 4am, this rarely happens. I happened once last year. When I've set the job to 3:30am, it's occurred six times. My guess is that there is a network issue and not a sql server issue, but I'd like to get some opinions from DBAs.
Thoughts as to what may be causing this?
August 27, 2009 at 2:43 pm
I would say it could be something (might be Network) causing this issue.
Before commenting on anything we have to investigate the system completely like
1. what DTS is doing?
2. at that time what all processes is going on?
3. any jobs run?
4. how many user are accessing the tables(objects) related to the DTS?
5. involve the network team to check that time?
HTH
Vinay
Thanx.
Vinay
http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay
August 27, 2009 at 2:51 pm
Before commenting on anything we have to investigate the system completely like
1. what DTS is doing?
2. at that time what all processes is going on?
3. any jobs run?
4. how many user are accessing the tables(objects) related to the DTS?
5. involve the network team to check that time?
1. DTS is importing data from flat file. Nothing fancy just taking the data from the file and inserting into the table no transaformations are occuring.
2. It's difficult to determine, but I'm not able to find jobs running at the time. Very, very low traffic on the box. The little traffic that was on was just select statements.
3. No other jobs running.
4. Maybe 2 or 3 users
5. This is where our problem lies. We really don't have a network specialist here to assist on this piece.
I'm leaning toward a network issue. From time to time, we have many of our backups, even across multiple servers to multiple fileshares, fail. I just don't know what to look for to go to our sys admin team to show that this is a network issue. Any advice you can offer would be greatly appreciated.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply