I have a question about the length of time that transactions run in DA. I've recently seen a case where the DISTRIBUTEDAGENTS::TaskType.Execute method had a transaction held open for over 30 minutes. It would have been longer except that we had to stop the service because the long transaction was blocking a number of table rows and preventing other threads from progressing. We've seen this a number of times. I backtracked the SQL connect logs to find the place in the code that most likely generated the output SQL and it's this method. Is this normal? I looked at the code and it seems like this might be a common occurance in a very busy system, especially if the machines where the DA run goes down for a bit and operations build up. I haven't spent a lot of time learning the DA system yet, so I'm just asking if this is a normal occurance and what process limits the transaction time?
