Three Ways Your Database Is at Risk

DBmaestro conducted a survey titled “Database Deployment & Development Risks” to gain insights into the risks associated with various database development practices. The survey focused on manual processes used throughout the development lifecycle.

The results revealed two divergent realities: despite participants from diverse sectors overwhelmingly recognizing the risks associated with manual process for the database, many organizations continue to use processes and solutions which do not fully automate the development cycle.

A Few Examples:

• Nearly 90 percent of survey respondents said there was a risk of one developer wrongly overriding valid changes with older revisions from other development branches when integrating changes. Still, more than half (53%) of the IT professionals surveyed, integrate changes, creating the possibility that such overrides may occur.

• Ninety percent of the IT professionals surveyed say that the database and version control repository to being out of sync represents a risk. But at the same time, 72 percent of those surveyed admit that their database may not be in full sync with the version control repository.

• Continuous delivery means full automation. This is often achieved in application development, but the database gets left behind due to challenges of implementation and risks involved with fully automating the delivery process. In particular, manual processes for generating SQL update scripts are still common in the database world, with 71 percent of survey respondents stating that they still rely on a manual process for generating these scripts.

Download the complete Database Deployment and Development Risks Survey Report and learn how to spot the risks to your database and build a more efficient development cycle.