C
ChUIMonster
Guest
It is always so much more rewarding when you do your analysis with your hands tied behind your back! Pointing -T at a slow drive would certainly be a potential issue. Especially if the -T space is actually being used. Are the files in that -T space active, large and growing? If they are then you should look at various client options like -Bt, -mmax, -TB, -TM and so forth and prevent as much of that disk use as possible. If SQL is involved make sure that you have updated the statistics. (You should also fix your code...) FWIW and IMHO in 999 cases out of 10 where someone is destroying the evidence on a routine basis (by, for instance, rebooting before you can see what is going on...) that person's area of responsibility is where this problem and the next dozen or so problems lie. While you are looking for processes that are not cleaned up -- check to see if there are perhaps a lot of CMD shells piling up. That is very easy to do if someone is improperly using .BAT files in this "batch processing" that you refer to.
Continue reading...
Continue reading...