dc/docs.datacontroller.io
3
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: adding more info on REPLACE loadtype
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 2m22s
Details

Browse Source
This commit is contained in:
Allan
2023-08-25 12:23:52 +01:00
parent 6db54d6b84
commit bc494d7e90
3 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/macros.md
View File

@ -36,7 +36,7 @@ The macros work dynamically, taking data types / lengths etc from the table meta
* High column volume
* New data types in CAS (Type 6 as well as 1 & 2)
Multiple load types are supported (full REPLACE, regular UPDATE, SCD2 loads, even BITEMPORAL). Composite keys are of course possible, so are retained keys (and the max key value can be table or data driven). Keys are taken from the staging table, so they could be based on an md5 hash, a UUID, or whatever you choose. It just needs to fit within the constraints of a SAS data step (so, max 32767 width for a character variable, 8 bytes numerical precision).
Multiple load types are supported (regular UPDATE, SCD2, format catalog loads, even BITEMPORAL). Composite keys are of course possible, so are retained keys (and the max key value can be table or data driven). Keys are taken from the staging table, so they could be based on an md5 hash, a UUID, or whatever you choose. It just needs to fit within the constraints of a SAS data step (so, max 32767 width for a character variable, 8 bytes numerical precision).
A column (eg PROCESSED_DTTM) may be nominated to retain the current timestamp when doing any type of upload.