Problem Context
Reading the Data Warehouse issue, I drew some distinct conclusions about what the textbook states.
Notice what the author explains in relation to transaction-oriented DW:
IunderstandthattheauthorstatesthatDWaretransactionoriented.
Nowseewhatitsaysinthefollowingparagraph:
Soon after, he says that DW are not transaction-oriented , which left me a bit confused since he is denying it.
My Understandings
When I read about it I understood that DWs are decision support tools that are query-oriented .
I understand that because they are focused on queries, bank might not respect the well-known normal forms (1FN, 2FN, 3FN) as they increase the amount of relationships and decrease the chance of duplication.
The fact is that the relationship in the bank affects the performance of queries because of the various'JOIN 'that are constantly being performed. >
DW is often very large since it serves as the central repository for all other databases.
Transactional database (Conventional) are concerned with non-duplication of record, so they tend to respect normal forms. These can be called transaction-oriented banks .
The data stored in DW has a NOT volatile characteristic, meaning that in the loading step, the data is filtered and cleaned, after this step the data only > suffer transactions from queries and exclusions , sem que possam ser alterados , this feature represents non-volatility .
Doubt
Are my understandings correct? Does the community agree in whole or in part with the statements listed above?
Remembering that the main focus of the question is in the title, ie can I really consider that the DW are query-oriented?
Source: Database Systems 6th edition, authors: Elmasri, Ramez Navathe, Shamkant B. Year: 2011 Cap 29, pg 720