Philip Arnold wrote: > > My problem with it is that if you put 3-4 queries inside a CFTRANSACTION > instead of using one TSQL transaction, then it'll have to "deadlock" the > DB Server for it to handle the transaction properly
Maybe for MS SQL Server, but databases that do "better than row level locking" have no problem with that scenario (Google for "Multi Version Concurrency Control" (MVCC) for the technical story). And the OP has never indicated that he used MS SQL Server (in fact, it said Access, so TSQL is not really an option and I don't know what transaction mechanism it uses). > Thus, using CFTRANSACTION on a clustered environment will work horribly > compared to writing it using transactions in a query or SP > > Say you want to do an insert, then get the Identity field, then do an > update related to that Identity, you're gonna cause real performance > issues, because the database can't handle the 3 commands as well as it > could if you wrote it decently in TSQL... There wouldn't be a deadlock. There would be extra overhead in issueing 3 queries with the extra network traffic, parsing and compiling, but not with deadlocking. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
