Time Invariant Data Base Instance: Difference between revisions
Jump to navigation
Jump to search
(Created page with "A Time Invariant Data Base Instance is a data base instance that ... * <B>Example(s):</B> ** a Subject-Oriented Time Invariant. ** an Integrated Time Invariant D...") |
m (Text replacement - ". ----" to ". ----") |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
** an [[Integrated Time Invariant Database]]. | ** an [[Integrated Time Invariant Database]]. | ||
** a [[Non-Volatile Time Invariant Database]]. | ** a [[Non-Volatile Time Invariant Database]]. | ||
** … | |||
* <B>Counter-Example(s):</B> | * <B>Counter-Example(s):</B> | ||
** a [[Time Variant Data Base]]. | ** a [[Time Variant Data Base]]. | ||
* <B>See:</B> [[Data Warehouse]], [[Subject-Oriented Data Base]], [[Integrated Data Base]], [[Non-Volatile Data Base]]. | * <B>See:</B> [[Data Warehouse]], [[Subject-Oriented Data Base]], [[Integrated Data Base]], [[Non-Volatile Data Base]]. | ||
---- | ---- | ||
---- | ---- | ||
== References == | == References == | ||
| Line 14: | Line 17: | ||
* https://docs.oracle.com/cd/B10500_01/server.920/a96520/concept.htm | * https://docs.oracle.com/cd/B10500_01/server.920/a96520/concept.htm | ||
** QUOTE: A common way of introducing data warehousing is to refer to the characteristics of a data warehouse as set forth by William Inmon: [[Subject Oriented]], [[Integrated]], [[Nonvolatile]], [[Time Variant | ** QUOTE: A common way of introducing data warehousing is to refer to the characteristics of a data warehouse as set forth by William Inmon: [[Subject Oriented]], [[Integrated]], [[Nonvolatile]], [[Time Variant | ||
*** [[Time Invariant Data Base|Time Variant]]: In order to discover trends in business, analysts need large amounts of data. This is very much in contrast to online transaction processing (OLTP) systems, where performance requirements demand that historical data be moved to an archive. A data warehouse's focus on change over time is what is meant by the term time variant. | *** [[Time Invariant Data Base Instance|Time Variant]]: In order to discover trends in business, analysts need large amounts of data. This is very much in contrast to online transaction processing (OLTP) systems, where performance requirements demand that historical data be moved to an archive. A data warehouse's focus on change over time is what is meant by the term time variant. | ||
---- | ---- | ||
__NOTOC__ | __NOTOC__ | ||
[[Category:Concept]] | |||
Latest revision as of 02:46, 24 September 2021
A Time Invariant Data Base Instance is a data base instance that ...
- Example(s):
- Counter-Example(s):
- See: Data Warehouse, Subject-Oriented Data Base, Integrated Data Base, Non-Volatile Data Base.
References
2013
- https://docs.oracle.com/cd/B10500_01/server.920/a96520/concept.htm
- QUOTE: A common way of introducing data warehousing is to refer to the characteristics of a data warehouse as set forth by William Inmon: Subject Oriented, Integrated, Nonvolatile, [[Time Variant
- Time Variant: In order to discover trends in business, analysts need large amounts of data. This is very much in contrast to online transaction processing (OLTP) systems, where performance requirements demand that historical data be moved to an archive. A data warehouse's focus on change over time is what is meant by the term time variant.
- QUOTE: A common way of introducing data warehousing is to refer to the characteristics of a data warehouse as set forth by William Inmon: Subject Oriented, Integrated, Nonvolatile, [[Time Variant