[AccessD] How does SQL Server do updates

Arthur,

You need to distinguish what's going on in the transaction log and on the data pages. The transaction log holds both the original and the changed records to enable a rollback, but that doesn't mean that the change on the data pages can't be in-situ. In fact I think it is: a delete-insert operation on the data pages seems ineffective to me.

Asger

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Arthur Fuller
Sendt: 9. oktober 2012 23:05
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] How does SQL Server do updates

Precisely my point, Jim. In-situ updates by definition destroy data and
prevent rollbacks; hence the delete-then-insert scenario, without which a
rollback would be impossible. Thus, UPDATE is a glorified term for DELETE
then INSERT. No other way to make it all work. Nuff said,,, or perhaps for
the sake of performance you would prefer to sacrifice RollBack.

A.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com