RE: true definition of a transaction
- From: "Leslie Tierstein" <leslie.tierstein@xxxxxxxxxxxxxxx>
- To: <ryan_gaffuri@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 3 May 2005 14:14:30 -0700
In a data warehouse, "transaction" is typically used to indicate the
lowest level of granularity of a base fact table. For example, I'm in
the process of writing a paper in which I included a sentence like:
The main fact table, for Point of Sale (POS) data, is aggregated to the
level of Item-Store-Date - we do not receive individual transactions.=20
So, a transaction could be in a 1:1 correspondence with a row of a fact
table maintained at the txn level of granularity -- which would be the
case if our DW contained actual POS data. The row in the DW started life
as an OLTP transaction, although, as you state, the DW DB did not
actually issue any corresponding commits.
=20
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
ryan_gaffuri@xxxxxxxxxxx
Sent: Tuesday, May 03, 2005 4:39 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: true definition of a transaction
Does the definition of a transaction vary depending on technology? The
high level definition is basically a 'single unit of work'. However, in
oracle a transaction is a commit, in J2EE EJB world a transaction can
include an in memory change to a variable, in sql server, i think
selects are included in the definition of a transaction.=20
I heard a guy on the radio who claims to run a company that 'implemented
one the highest transaction data warehouses in the world'. To me that is
an oxymoron. By definition data warehouses are read mostly, with period
data loads.=20
has anyone else noticed this? any comments?=20
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
