Hey Jeffrey thanks for chiming in.
Let me clarify what’s happening. There is a delete query and an insert query wrapped in a Begin Commit/Rollback Tran. Some of the data is deleted and some left in the table The data being queried from the other job is specifically the data that’s being deleted and then reinserted, so upon completion of the commit it should return data. What’s happening is there are inconsistent results on occasion (either no data or not the same amount of rows) being returned. I mentioned read committed because it’s the default setting and since there are no query hints and they’re just basic delete/insert/select statements that isolation level should be applied. It’s an interesting scenario and I’ll try and provide more detail when I can.
Hmmm.... in your original post, you clearly stated "I have another job that on occasion reads data during this update and returns no data. "
It sounds like you've changed the problem a bit. Now you're saying "upon completion of the commit it should return data". At that point, if it's not, then perhaps one of two things is happening... the commit hasn't happened like you think it has or the delete/insert code is actually bad and not adding the right stuff.