Q and A

Asked and Answered

As you mention in your article "Tuning Up for OLTP and Data Warehousing" — http://www.db2mag.com/db_area/ archives/2002/ q3/hayes.shtml — all user activity in a DW environment is read only. What's the impact of changing the locksize for tables from the default of ROW to TABLE?

Scott Hayes responds:

Using locksize TABLE is an excellent idea when access to a data warehouse is read-only. The big savings comes from CPU cycles saved when DB2 doesn't have to manage all the row locks. If CPU utilization is high on the machine, the CPU savings may even translate into elapsed time improvements for queries.

See a complete archive of reader/author Q&As .