this post was submitted on 26 Sep 2023
2 points (100.0% liked)

Data Engineering

1 readers
1 users here now

Discussion on Data Engineering topics. Data pipelines, tools and technologies, databases and DBMS, best practices:

Rules:

founded 1 year ago
MODERATORS
lucas50a@lemm.ee
2
The 6 columns essential to a $6B/year database table (self.dataengineering)
submitted 1 year ago by greengnu to c/dataengineering@lemm.ee
2 comments fedilink hide all child comments
 

When you have a database with 6 Billion dollars (US) flowing through it every year, you need to be able to account and prove exactly every single penny and every single action that occurred. So you better have _A tables for all of the main tables and have these columns to boot.

  1. Create_user_id – Who/what created the record
  2. Create_Dt – When exactly was this record created
  3. Update_user_id – If updated, who updated this record (default null)
  4. Update_Dt – when was it last updated (default null)
  5. Archive_Dt – When can we legally destroy these records
  6. Unique_Trans_id – So that tracing down everything that occurred becomes even easier.

It isn't sexy but it'll be handy if you ever need to trace down things in your database too.

you are viewing a single comment's thread
view the rest of the comments
[–] cestvrai@lemm.ee 2 points 1 year ago (1 children)

So, if edited multiple times there is no record of who made previous changes?

[–] greengnu 2 points 1 year ago

incorrect, all of the previous versions and who made those changes would all be stored in the _A tables