top of page
DVUG Meetup Image (1).jpg

Veronika Durgin

What to do (or not do) when implementing a Data Vault - lessons from the field

Recurring implementation mistakes in Data Vault projects reveal where teams misapply modelling principles and how better delivery choices emerge.

Thinking Icon White (1).png

Best practices for Data Vault implementation

Thinking Icon White (1).png

Common Data Vault pitfalls and traps

Thinking Icon White (1).png

Real‑World Lessons

Introducing the Presenter

Veronika Durgin

Head of Data

Veronika Durgin is a database professional with over two decades of experience. Her passion for all things data led her on an incredible journey from a Junior SQL Server DBA to her current role as the Head of Data.
Veronika is "passionate about all aspects of database design, architecture, engineering, and performance tuning".

Driving business value – What to do – and not to do – In Data Vault

The journey from learning about the theory of Data Vault, to becoming a qualified practitioner has a lot in common with the way in which you learn to drive a car – regardless of which country you live in.

Download Your FREE Slides Now


Please note that by downloading these slides, you join our Data Community. We encourage you to join our forum and we may send occasional emails of the latest news, updates, and insights from the community.




Related Content

5 most common challenges with Data Vault modelling

From modelling complexity to integration overhead, recurring Data Vault challenges reveal where architecture decisions most affect long-term maintainability.

More

Accelerate your Data Vault journey with the power of erwin Suite

Using the erwin Suite, organisations can speed up Data Vault adoption through automated design, stronger governance controls and more efficient modelling workflows.

More

Agile building of Information using Data Vault 2.0

Applying agile principles to Data Vault 2.0 supports incremental delivery of structured information while maintaining governance and architectural consistency.

More
bottom of page