I'm wrestling with the decision of whether to use PAGELOCK OFF in one of my bigger X Enterprise databases. Looking at all the "help" documents it seems like the only reason you would want pagelock On (the default) is if you are updating all the rows in a table, with no "where" clause. As in this help example:
-- The UPDATE must alter the values for many rows SET PAGELOCK ON -- use page locking UPDATE <tablename> SET <columnname> = value -- no WHERE Clause SET PAGELOCK OFF -- use row locking So, if I have heavily-used tables with millions of rows and never update without some kind of Where clause, and if the only tables where I might update all rows would be much tables, there's no reason to keep the default Pagelock On is there? And I"m guessing that no one knows if there's a threshold where you would want to set it back to On, say if you used a where clause that would update a couple hundred or thousands of records? Or is Pagelock On ignored if there's any kind of where clause? I've never changed the default Rowlocks On setting, so I'm good there. Opinions? Anyone who's recently changed from On to Off and noticed a difference? Thanks everyone! Karen -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
