In addition to that, DBAs deploys the updates to the database manually, ignoring the CI/CD process, even when there’s one. It’s not they are they are lazy, but it is because they have their own process (in most cases not agile) and they need to make sure their SQL scripts are really optimised and well tested.
And if developers ask them for an update, they will take so long to do it. They use their own tools and manages the database as it’s their own property.
Dbschema vs dacpac update#
The point is that both changes to the app and the database must be deployed together during the same deployment process.īecause, if we update only the app’s entity, the app will try to find the corresponding column in the database, it won’t find it, thus it will fail.Ī bad practice is being done today is that DBAs are working in a separate team than working with developers. This requires 2 changes: updating the entity in our app’s code and also updating the SQL script for the product table. For example, we need to add a property Color to our products. Because, in a new app update, we might also change the database schema. By saying the app, we mean the entire app including the database. The objective of DevOps is to create a process for safe, secure and even more frequent delivery for the app.
CI/CD for the app (Dev), database (DBA) and infrastructure (Ops) Why adding the Database to the CI/CD pipeline ?
0 kommentar(er)
