July 1, 2014 at 9:56 am
Next time it hangs, before restarting anything, can you run each select statement separately and as 1 to see they all run?
And maybe without NO LOCK check also to see if dirty reads are causing something?
Don't understand why you would need NO LOCK, but hope you know why.
July 1, 2014 at 9:58 am
Oh i will.
NO LOCK features heavily throughout the procedure. Shouldn't really be an issue (as it runs at 1am normally), but better safe than sorry
July 1, 2014 at 10:34 am
peter.cox (7/1/2014)
Oh i will.NO LOCK features heavily throughout the procedure. Shouldn't really be an issue (as it runs at 1am normally), but better safe than sorry
More concerned about the possible data integrity than performance for NO LOCK.
I never found a need to read dirty records.
Don't know why you would call reading an uncommitted record that could be rolled back 'safe'.
Note that I am suggesting seeing if the query can run and select data at the stoppage point, without inserting new records.
And maybe running a trace to see if something shows up.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply