We have a client that has their own dev server in addition to a local dev server that we have and control. Each parties already have a copy of the code and database with the site running. The client requested that future database change releases needs to be delivered in SQL scripts instead of database backups. We are not sure how to proceed or even know if it is possible since the each release will probably also affect the database schema. My best guess is to use a comparison tool like SQL Compare and manually script the changes from the old and new database. I realize this also can be dangerous and will most likely break some things. Can anyone share any light on this?
Once in a while, the database will be changed outside of added pagetypes. For now, our client decided to use the import/export method of adding new pages. We may not have to rely on SQL scripts anymore.
We have a client that has their own dev server in addition to a local dev server that we have and control. Each parties already have a copy of the code and database with the site running. The client requested that future database change releases needs to be delivered in SQL scripts instead of database backups. We are not sure how to proceed or even know if it is possible since the each release will probably also affect the database schema. My best guess is to use a comparison tool like SQL Compare and manually script the changes from the old and new database. I realize this also can be dangerous and will most likely break some things. Can anyone share any light on this?