[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Question about transaction that spans MSS DataServer and OpenEdge DB

  • Thread starter Thread starter dbeavon
  • Start date Start date
Status
Not open for further replies.
D

dbeavon

Guest
So based on that, it sounds like a SQL Server error message is the "good" one to look for because it almost certainly means that updates on both the SQL and OE side of things will be properly rolled back. On the other hand, an error message from the OE database (ie. unique constraint violation for example) may be a much more scary one ... because there is a possibility that the error message could arise *after* the SQL Server update operation has already committed. (IE. the OE database update operation is to be rolled back, but the SQL Server update will not.) This is nice information to know. Have you ever seen this type of thing in documentation? Personally, I would rather that this would have just failed by default (ie. with an optional parameter, -feelingextremelylucky, to allow the two databases to participate in the same "transaction").

Continue reading...
 
Status
Not open for further replies.
Back
Top