Hot answers tagged

15

Pramod Sadalage and Scott Ambler wrote a book Refactoring Databases: Evolutionary Database Design that is an incredibly solid primer to the subject of DBs in a CD org/team.


13

The Challenges I am aware that there are practices such as only adding database objects, i.e. tables and columns, never modifying or removing them At one company I worked for, a rolling window of raw data equated to about 6 months and ate up 10 TB. The data was then processed into an RDBMS format which cost 6 TB of usable data which accounted for about ...


9

I would integrate the schema management into the application itself (or along with it). Any change to the schema should be committed along the application code (and hence tagged also). There's already a bunch of possibilities listed in this question: What practices or tools enable Continuous Deployment of Databases With this kind of tools, using an in ...


6

We use Flyway at work for managing Postgres schemas in the app, and Pillar for managing Cassandra schemas. We have found it best if the app manages its own schema. We had a horrible experience having ansible manage schemas before the apps managed their own schemas.


6

I'd argue a tool alone won't really help unless you shift the schema responsibility to the application team. We do use liquibase or flyway at work, where the application team is responsible to create the changesets. Along with this,you can avoid a purely additive way. Each application is required to be compatible with its precedent version, when an ...


4

In our company we manage our application code within a VCS (Git) and most of the applications we work with install their core database from within the setup scripts that ship with the application. If we would have to extend or customize an application for one of our customers which involves having to extend the database or do database customizations, then ...


4

To answer this question in the context of a mainframe environment, and specific to DB2® databases, there are typically 2 commonly used (not cheap ...) alternatives to pick from: Object Administration for DB2®, from BMC. Here are some details about it (quote from the linked page): Making changes to objects in your database—or even just performing routine ...


4

We use liquibase at our work and I'll speak highly for it. It's also used by our QA tool QASymphony. We're utilizing it against MSSQL and Oracle databases internally and QASymphony uses/has used it with both postgres + mysql instances.


Only top voted, non community-wiki answers of a minimum length are eligible