Comments
Sort by recent activity
Hy Tianjiao, we have a few developers working on our shared database on different issues for different releases. When they finish their work, they commit the changes with an appropriate comment with Source Control. If they get notified that there are "dependent changes", they do not automatically include them but they go through them afterwards (because most of the time, the dependent changes are not relevante for their work). On the day of the release, our release manager goes through all the commits and selects every single commit that is relevant for the release and creates a single migration script.This migration script is exceuted on our internal productive-database for our testing-department. If all the tests are OK, the release-manager sends the script to DBA's of our customer to execute the script at our customers database to finish the release. It would be great if there is an "alternative way", because this release-process is coordinated with our customer and we are not allowed to change the process. And in the meantime it's very time-consuming and error-prone to create the script for each change manually. BR, Manuel / comments
Hy Tianjiao,we have a few developers working on our shared database on different issues for different releases. When they finish their work, they commit the changes with an appropriate comment with...