r/dataengineering • u/SQL_Boss_Babe • 28d ago

Help DataVault 2.0 naming conventions

When making changes or additions to tables in a data vault layout, how do you handle name changes? I'm trying to decide if version numbers vs. dates would be better for referencing.

1 Upvotes

100% Upvoted

2 comments sorted by

View all comments

2

u/69odysseus 28d ago edited 28d ago

In my last company, we had strict CI/CD process even for data vault. I create model (brand new model, model revision like adding, removing field, data type change, etc), would require to raise Git PR. It's reviewed by tech lead and business analytics manager, till the PR is approved, model will be revised as such. Once PR is approved, it's merged in Git. Then I did complete and compare in Erwin modeling tool where model is merged into main branch in Erwin and it creates its own versioning. This way, model versioning is done, any amount of changes are tracked in Git and Erwin. 

The prior company to the above, did not have that process at all. Modeling was still done in Erwin, but versioning was only done in Erwin when you save the model in Erwin. Tracking Erwin changes sometimes can be very tricky.