Re: Db2, Oracle, SQL Server

> > In some cases, leaving the locklist small and encouraging lock
> escalation is
> > good, because row locks are more expensive (time consuming) than
> table
> > locks, especially if concurrency is not an issue.
>
> When concurrency is not an issue, Access will usually provide an
> acceptable solution.
>
> --
> MJB
Maybe you are not familiar with large data warehouse databases? You can check the TPC-H benchmarks at http:/www.tpc.org to get some idea of the size of a typical data warehouse database.

If you have a data warehouse (decision support) database, concurrency is not a problem unless you are trying to load data a the same time as you allow people to perform queries. DB2 and Oracle allow multiple share locks to occur simultaneously with any concurrency problems.

In this sub-thread discussion (as well as the normal usage of the term) concurrency means ability of multiple users to access the same data with Locking Problems.

The ability to access the same data without performance problems is a different subject, and not the same thing as concurrency. Received on Sun Feb 06 2005 - 17:12:06 CST