D
dbeavon
Guest
I wrote my first ABL transaction against MSS dataserver just now. The very next thing I tried after my SQL Server transaction worked was to update a record in an OE database during the same DO TRANSACTION block. In other words, the "DO TRANSACTION" block was used to make updates to both the OE database and the SQL Server database. That worked without any errors - which is a bit scary. I am going to bet that there was little going on insofar as transaction coordination or two-phase commit. And each database has its own transaction log which opens the possibility for one side to get rolled forward while the other rolls backward. I'm assuming that there are best practices that tell people *not* to do this type of thing? But given that developers aren't prevented from doing this, how will we manage it when these types of transactions generate an error? Should we continually check the databases to look for committed data on one side and not on the other? Can we assume one type of database always commits before the other (ie. OE before MSS)? Any help would be appreciated. I found a number of resources related to MSS dataserver but nothing that talked about transaction coordination between OE's DBMS and MSS. Thanks in advance, David
Continue reading...
Continue reading...