EDW-2011-Johnston

Recommendations

Info

CONCLUSIONBitemporal data management is becoming mainstream.DBMS and other vendors support it right now!A vendor solution is an enterprise solution, replacing differenthome-grown ways of supporting temporal requirements.The maintenance of bitemporal data is complex. One temporaltransaction may take a dozen or more physical SQL transactionsto complete.Vendor solutions hide the complexity, by mapping the onetemporal transaction to the multiple physical transactions “underthe hood”.Slide 62.EDW 2011Understanding Bitemporal Data. © 2011, Asserted Versioning, LLC
QUESTIONS1. How do Kimball’s slowly changing dimensions compareto bitemporal data’s way of keeping track of changes?2. The maintenance of bitemporal data is complex. One temporal transactionmay take a dozen or more physical SQL transactions to complete. Do wehave to write those physical transactions? If not, how do we avoid it?3. These bitemporal tables are complicated! How do wehide that complexity for queries against bitemporal data?4. Rows in bitemporal tables contain a lot of extra columns.Will every change result in one or more new rows? If so, willstorage space be a problem if we use bitemporal data?5. How can bitemporal data be made to perform as well as non-temporal data?6. How much work will be involved in swapping out DIYsolutions for vendor-provided bitemporal solutions?Slide 63.EDW 2011Understanding Bitemporal Data. © 2011, Asserted Versioning, LLC
Page 1 and 2:
UNDERSTANDING BITEMPORAL DATADetail
Page 3 and 4:
READINGSRichard T. SnodgrassDevelop
Page 5 and 6:
PRODUCTSOracle 11g, Workspace Manag
Page 7 and 8:
PRODUCTSThe Asserted Versioning Fra
Page 9 and 10:
Part IITwo Kinds of ChangesSlide 9.
Page 11 and 12: TWO KINDS OF CHANGESThings change s
Page 13 and 14: TWO “WHEN” QUESTIONSWhen were t
Page 15 and 16: NON-TEMPORAL DATAclnt-idtxn-dtnameT
Page 21 and 22: Part IVPoint in Time VersioningSlid
Page 23 and 24: POINT IN TIME VERSIONINGclnt-idtxn-
Page 25 and 26: POINT IN TIME VERSIONINGclnt-idtxn-
Page 27 and 28: Part VDelete Flag VersioningSlide 2
Page 29 and 30: DELETE FLAG VERSIONINGclnt-idtxn-dt
Page 31 and 32: DELETE FLAG VERSIONINGclnt-idtxn-dt
Page 33 and 34: PERIOD OF TIME VERSIONINGclnt-id ef
Page 35 and 36: PERIOD OF TIME VERSIONINGclnt-id ef
Page 37 and 38: VERSIONS VS. CORRECTIONSclnt-id eff
Page 39 and 40: Part VIIIPeriod of Time PK Versioni
Page 41 and 42: Part IXBitemporal DataSlide 41.EDW
Page 43 and 44: BITEMPORAL DATAclnt-id eff-beg-dt e
Page 45 and 46: BITEMPORAL DATAclnt-id eff-beg-dt e
Page 47 and 48: Part XHiding the Complexities With
Page 49 and 50: VIEWS: A VERSION TABLEclnt-id eff-b
Page 51 and 52: VIEWS: A NON-TEMPORAL TABLEclnt-idn
Page 53 and 54: Part XISome Important ViewsSlide 53
Page 55 and 56: VIEWS: HISTORY/VERSION TABLES• In
Page 57 and 58: Part XIIVersioning,Standard Bitempo
Page 59 and 60: STANDARD BITEMPORAL DATACurrent Dat
Page 61: Part XIIIConclusionsSlide 61.EDW 20
show all

EDW-2011-Johnston

Create successful ePaper yourself

Delete template?

Save as template?