Recipe 15Sending Upgrades to Customers

Problem: Sending new releases of an application to customers means a lot of work for the developer team, and the upgrades are prone to errors

Determining what version of the application database the customer is running and then sending the correct upgrade is always a problem. Customer database upgrades require a lot of effort from a development team.

Solution

The solution is remarkably simple when you follow the recipes outlined previously, and you have sequential change scripts that are version controlled and named with your preferred method. The following example of an upgrade script upgrades a customer database from Release 1.2 (Jupiter) to Release 2.0 (Pluto), which also upgrades the application build ...

Get Recipes for Continuous Database Integration: Evolutionary Database Development now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.