Procedure getting stuck at a particular SQL Data reader step

Question

a {    text-decoration: none;    color: #464feb;}tr th, tr td {    border: 1px solid #e6e6e6;}tr th {    background-color: #f5f5f5;}

Hi everyone,

Has anyone faced a situation where a Data Reader shows 100% progress but still remains in the “Reading” state for a long time and does not exit?

In our case, the records appear to be fully processed, but the step continues running until it is manually stopped.

What is the recommended approach in this scenario?

* Is it safe to stop the procedure and rerun it?
* Are there any known DB-side or BOARD configuration causes for this behavior?

Additionally, what is the best way to stop such a procedure?

When clicking the Stop icon, it does not work, and we usually have to restart the BOARD service to clear the process.

Appreciate your inputs and experiences.

Robert Barkaway · Answer

Okay that would definitely suggest a timeout somewhere along the line then, if it's only happening occasionally when things are a bit slower it's probably just getting in within the timeout window the rest of the time and a bit of slowdown is enough to carry it over.

Arul Judes · Answer

Thanks, Robert. I will check this.

This issue does not occur on a daily basis. In fact, it happened only on four specific days this month, always at the same step. During those days, the SQL DataReader startup itself was slow—it usually completed the initial 20% in about 5–10 minutes, whereas the ideal total runtime for the entire SQL process is around 23 minutes.

Robert Barkaway · Answer

Okay if I had to guess I'd say the connection is timing out and Board is losing comms with the SQL session, which means that it's waiting for more data and not realising that the session has ended. Look at your timeout settings and try increasing them to see if that helps. The only other time I've seen something like that is where there's actually a network drop and the connection is lost that way, but that wouldn't happen every time typically.