For this months T-SQL Tuesday contribution I want to cover how you can improve your Data Platform integrity with CI/CD practices.
Before I go any further, I want to thank Rob Farley who hosts this months T-SQL Tuesday. Rob invites us all to cover the topic of integrity.
You can read the original invitation by clicking on this link for the T-SQL Tuesday 182 invitation. Alternatively, you can click on the image below.
Improve your Data Platform integrity with CI/CD practices
I know that introducing CI/CD practices improves your Data Platform integrity because I have done it to scale.
When I say to scale I mean that I helped deliver a large-scale project that introduce CI/CD practices. Which I partly mentioned in previous posts. Including my T-SQL Tuesday 169 contribution.
I know some people are wary about introducing CI/CD practices. However, they can bring you massive benefits and enhance the integrity of your development.
Even more so when you introduce automated tests into your pipeline and introduce practices like shift-left testing to catch issues early in the development process. Yes, it can take some effort to do but the benefits of doing this pays off.
In addition, automating as much as possible keeps a visible audit trail of all the activities. Including when changes were committed to your Git repository. Which makes it easy to show the integrity of your CI/CD practices to both stakeholders and auditors.
Final words
I hope me my T-SQL Tuesday contribution this month provides food for thought.
Because this is a topic I am passionate about. Due to the fact that I honestly believe that the effort to put CI/CD practices in-place pays off.
Of course, if you have any comments or queries about this post feel free to reach out to me.
Be First to Comment