Deploying schema changes and database code to a live server can be a nerve-wracking experience fraught with danger with every script. The smallest error can cause untold amounts of downtime, this is bad for in-house systems but for ecommerce systems its catastrophic. Database changes are permanent, there is no ‘undo’ , there is no rollback. There is no safety net. If something goes wrong we have to fix forward, let us hope that we get that right and not compound the error. We cant just put back the old code and revert to a previous version. In this session we shall look at the options of deploying database changes, and how we can automate many of the manual steps involved. 

(no tags)