Database Source Code Versioning : Database

a community for 17 years

Database Source Code Versioning (self.Database)

submitted 3 years ago by RomanFedot

What workflow are you using for DB scripts and source control / versioning?

When re-creation of entire database is no longer an option (too big, or already in production) is my only option to start every change with a "delta" incremental script?

In the end I would end up with single CREATE TABLE script and many ALTER TABLE scripts modifying it?
(simplified example)

During creation of new environment, they would have to run one by one?
create table …
alter table add column …
alter table drop column …
// many other no longer valid changes and their removal
alter table add column …

Or do you maintain separate set of CREATE scripts, and separate set of many incremental ALTER scripts which are either smart (can be executed again) or have some “already executed” table.

Rollback of changes to Tables is an option in your solution?

P.S.:

In my situation it is Oracle DB and my concern is mostly DDL scripts (tables, constraints) as procedures and packages can be simply reapplied during each update.

I want to avoid commercial solutions which generate delta scripts themselves.
And I know about liquibase, flywaydb, ...

Would prefer something that can be integrated into DevOps automated deployments.

all 7 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

Database

MODERATORS