Posts Tagged with automated deployment
If you’re struggling to set up a reliable, repeatable release process you’re not alone. The good news is that most of the problems you’ll encounter have been solved before. There are many smart strategies you can use to create a fast, smooth release process that will give your entire team a competitive edge. Tip... Read more
The final part of Alex Yates's three-part series tackles the complicated issue of automating deployments when the same table might have a different structure, in different production versions of the database. Read more
In Part 2 of his series, Alex Yates shows how to use a combination of post-deployment scripts to handle cases where a code object exists in multiple production instances, but in different states. Read more
How to use filters in SQL Compare to avoid deploying objects that exist only in the source to databases where they may not be required or appropriate. Read more
For the SQL Change Automation team, it’s important that we take time out from development, occasionally, to explore some of the issues our customers face when automating database deployment. Following on from previous posts about cross-database and cross-server dependencies and production database drift, this article shares some of our thoughts about how to deal with database... Read more
For the SQL Change Automation team, it’s important that we take time out from development, occasionally, to explore some of the issues our customers face when automating database deployment. Following on from previous posts about cross-database and cross-server dependencies, this article shares some of our thoughts about how to deal with production database drift. If... Read more
The SQL Change Automation team here at Redgate occasionally take time out from development to explore some of the issues our customers face when automating deployment of database changes. As part of one such exercise, we took a closer look at cross-database and cross-server dependencies – these can cause problems when deploying databases to multiple... Read more
Deploying database changes to new environments is a very stressful activity. Many organizations and their employees dread migrating changes to a production database because of the potential for problems or downtime. There are ways to minimize the potential issues and build more reliable deployment processes. In fact, many organizations do this, but they do... Read more
Reliability, traceability, speed: these are the top three motivators for automating the deployment of database changes. Especially when it comes to production, there is no compromising on the level of scrutiny that may just prevent something disastrous happening in production. This need for quality has a strange effect. We talked recently to 30 teams at various stages... Read more
From a business risk perspective, data change can be just as significant as code or schema change. Sometimes even more so; an incorrect static (or reference, or master) data change can drive your software’s behaviour more dangerously askew than pretty much any bug can. Imagine treating a retail customer for an investment fund as a corporate... Read more
