progress
-
Hi
we have a user who is running a very long update query on SQL2k service
the user is the only user on this service and the query has been running for 33 hours - he is updating a 37mil row table from a join on a 23mil row lookup table.
We expected it to take time, but it is taking longer than we expected. Our investigations suggest that he failed to index the lookup!!! So we know why it's taking so long...
We have tested on a similarly specced machine how long a smaller update takes and guestimated that the full query may take another 4 hours. But we could be very wrong and it could continue for days more given the poor design of his query and failure to index!!!
We have become involved because there are other larges jobs that need to go onto this service and he is now well over his allotted time...
We have two options:
1) let it run out
2) stop, rollback, index, run again
Is there a way we could test the progress before we make this decision?
-
This was removed by the editor as SPAM
-
actually trhis is a dead issue, no need to respond!!!
unless you have something to say...
-
maybe just some CPR
split the updatequery in chunks so it does not lockout the whole of the table (unless you realy need the full update at a single point in time available)
otherwize it will be RIP again if he/she launches it
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply