How to Effectively Monitor SD-WAN and SASE Environments with ThousandEyes
Database Change Management
1. Database Change Management One solution to an often complex problem Kevin Hurwitz Headspring Systems [email_address]
2.
3.
4.
5.
6.
7. Database Schema Change Lifecycle Time Developer creates an incremental SQL change script and tests the change locally Once the change is validated by unit tests, the script is checked into source control in a special location The automated build process kicks off, runs the upgrade process which executes the change script against the integration test database, and runs all unit tests to validate the change Once the build has succeeded, the tester can get the latest version of the software from source control and run the upgrade process via a GUI to upgrade her local database Once the build has been validated by QA, automated build processes can be run to deploy the software to staging and production
8. Creating SQL Server Change Scripts Time Developer snapshots the current state of the database using Red Gate SQL Compare Developer makes all necessary changes to the database using SQL Server Management Studio Developers executes Red Gate SQL Compare to create a transactional change script for the change just made in SQL Server Management Studio The developer saves the Red Gate change script within the database script project under the “Update” folder The developer rebuilds the database from scratch, re-executes the database integration unit test, and commits the new script
![Database Change Management One solution to an often complex problem Kevin Hurwitz Headspring Systems [email_address]](https://image.slidesharecdn.com/database-change-management-111002152243-phpapp02/85/database-change-management-1-320.jpg)
![The Problem ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)