What is Database Continuous Integration?

Question

What is Database Continuous Integration?

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004392 More actions · Answer 1

Heh... continuous integration is the only way that you can make the maximum number of mistakes before anyone can even blink because, although humans can really make a mess of things, it takes a computer to really screw things up quickly. 😛

We don't even attempt it anymore.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Phil Parkin SSC Guru Points: 246971 More actions · Answer 2

We have a TeamCity (TC) server which we use to automate many repetitive jobs, in the spirit of CI.

Such things include:

1) Moving changes from source control to QA databases

2) Building and deploying SSIS ispac files

3) Creating drift reports for production databases

4) Running Powershell scripts to check (and set) server config settings

5) Sending alerts if certain production database criteria are met

6) Sending alerts in the event of build failures for QA or production databases (we use VS database projects)

7) Building and deploying web sites.

The next thing we intend to automate is the restore of prod databases to QA. I know that this can be done outside of TC, but not with the same level of ease and visibility to non-SQL Server users.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

mcmangold SSC Enthusiast Points: 161 More actions · Answer 3

Steve,

I am not sure what VCS stands for in the phrase "There are people that follow a change script process, producing and saving .Sql files for all changes in VCS" or in "If you're using a VCS, and you should be, you'll have copies of old code to easily undo a change if it's a mistake" -- are we talking Version Control System? Please expound. Thanks.

Marty

Peter Schott SSCrazy Eights Points: 9675 More actions · Answer 4

mcmangold (6/2/2015)
Steve,
I am not sure what VCS stands for in the phrase "There are people that follow a change script process, producing and saving .Sql files for all changes in VCS" or in "If you're using a VCS, and you should be, you'll have copies of old code to easily undo a change if it's a mistake" -- are we talking Version Control System? Please expound. Thanks.
Marty

You've got it right, Marty - Version Control System. (Git, TFS, etc. even Source Safe might qualify 🙂 )

mcmangold SSC Enthusiast Points: 161 More actions · Answer 5

Thanks, Peter! I've been around TFS before, but found it used for front-end application code only, not involved with database updates. I'd be happy to see a separate topic thread on this sometime, including the Build-Your-Own (RYO) variety.

Thanks again.

Marty

Peter Schott SSCrazy Eights Points: 9675 More actions · Answer 6

Well, we used SSDT SQL Projects for our databases. We used Git for version control, but could have used anything - it's just files behind the scenes. To push the changes, we used Jenkins, but again any platform can work there with a little work.

I've also seen people roll their own sets of scripts, making each change idempotent so it can be rerun at any point. Those changes are then rolled up through some other interface that knows how to interpret the files. There are even some packages that handle that as the norm - DBDiff does that, IIRC. I'm a bigger fan of the Red-Gate or MS method overall. They basically say "I want the DB to look like this - make it happen". Both have support for smart renames so you shouldn't have to worry about someone renaming an object and the compare thinking that this means "drop old, create new".

Steve Jones - SSC Editor SSC Guru Points: 736342 More actions · Answer 7

Thanks, Peter.

Apologies, Marty. I do try to spell out the acronyms most times, but didn't hear. VCS is Version Control System, also known as Source Control. I'll try to do some more writing and produce some content on using your database with a VCS.