Posts: 1
Registered: ‎05-08-2020

Better versioning practices of database scripts

We usually version our Scripts in source control every time a developer make any changes in the database we usually script the changes and create an SQl file and persist that in the source control. But this practice is kind of making us feel that we are over complicating things and the chances of missing the script are high so one thing comes to our mind was to integrate the SQL project which is available in visual studio and with that whenever a developer make any changes they can directly checkin into that SQL project and with very little effort we can compare the SQL project to any database instance of any environment we have and during the CICD process we can generate the script dynamically using some CLI. Is that something which is considered a better price or are there any other ways to do the versioning of the database? how you guys are doing that?