"Noons" <wizofoz2k_at_yahoo.com.au> wrote in message
news:42073e33$0$27615$5a62ac22_at_per-qv1-
> > decision support databases were the data was only loaded when the table
is
> > not available to users, or when the table is available to users and only
> > selects are being executed.
>
> Just take a full table lock at the start and be done with it.
> It's a very special case, the loading of DSS or DW data.
> >
For decision supports systems, it is not a unique occurrence. It is not just
the loads. It applies to the loads, utilities, and all queries. You don't
want a "select" only system to take row locks all the time, because table
locks are much faster. Storing locks in memory is also faster than storing
them on the blocks.
If running an OLTP application, it is quite easy to set the locklist memory
in DB2 to sufficient levels to prevent lock escalation. Even a child could
do it.
Received on Mon Feb 07 2005 - 08:51:50 CST
