> not accurate 100% of the time. If you follow the link to the
> <cflock> devnet article from the URL I posted, it explains this.
According to that article:
"Serializable isolation level transactions are the most data-consistent
transactions, but also have the most overhead. A serializable transaction
places an exclusive lock on every data-table in use for the duration of the
transaction. Essentially, access to database tables is single-threaded when
you use serializable transactions. Because serializable transactions use the
highest locking levels, best practices discourage using it."
By that logic - your logic from the article you wrote - you should never
need to use CFLOCK in conjunction with CFTRANSACTION to get the values you
should. And, your logic was absolutely right! Here's part of what SQL Server
Books Online says about serializable transactions:
"Places a range lock on the data set, preventing other users from updating
or inserting rows into the data set until the transaction is complete."
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
