row level vs page level locking is it more than marketing hype? was Re: Informix vs. Sybase vs. Oracle vs. (gasp) MS SQL Server

>>>>> "Gary" == Gary Kuever <gkuever@ix.netcom_remove_this_.com> writes: Gary> Gary> 2 - On the minus side of row locking, it encourages developers to continue Gary> with a record oriented mentality instead of a set mentality. An example is Gary> Oracle's row_id. I've seen this on every Oracle project, i.e. the shortcut Gary> is taken instead of thinking the set operation through properly. Gary> ... and of course you end up with crappier performance with the row at a time vs set based approach. I was doing a bench for a customer and they were doing some nightly processing... looking at their code, I saw that one section was taking 2.5 hours. I rewrote it and that same section took a couple of minutes. What was the magic? Converted their row at a time logic to set based logic. -- Pablo Sanchez | Ph # (650) 933.3812 Fax # (650) 933.2821 pablo@sgi.com | Pg # (800) 930.5635 -or- pablo_p@pager.sgi.com ------------------------------------------------------------------------------- I am accountable for my actions. http://reality.sgi.com/pablo [ /Sybase_FAQ ]