Why does TPC-D model a system which supports concurrent updates?
A pure decision support environment need not support concurrent updates because decision support applications themselves tend to be largely read-only. That TPC-D models a system supporting concurrent updates is one manifestation of the “worldwide” database model upon which TPC-D is based. The database is viewed as one which can support both queries and updates throughout a 24-hour period from end users all over the world, with no regular sustained quiescent period during which maintenance (for example, reorganizing or reloading) could be done. The major ramifications of this are that a DBMS must support database locking as well as the ACID properties of transaction processing systems.
Related Questions
- Do I need to install any software on the local system to use Sun Update Connection, System Edition software, or can I manage updates only from the hosted web application?
- Where do I go to get the latest system updates newsletter or important messages?
- Why does TPC-D model a system which supports concurrent updates?
