RE: Sql Server Patch Scripts

Oops –I replied to the wrong email ☺ From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Ken Schaefer Sent: Tuesday, 3 November 2015 10:42 AM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: RE: Sql Server Patch Scripts The other option might be t

RE: Sql Server Patch Scripts

] On Behalf Of David Burstin Sent: Monday, 2 November 2015 3:16 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: Sql Server Patch Scripts We use SQL Server projects for patching, version controlled with git. For schema changes, we run a compare on the project and the dev database (as

RE: Sql Server Patch Scripts

| Web: www.sqldownunder.com<http://www.sqldownunder.com/> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Ken Schaefer Sent: Tuesday, 3 November 2015 10:44 AM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: RE: Sql Server Patch Scripts Oop

RE: Sql Server Patch Scripts

Hi Tony, We use dbup (https://dbup.github.io/) - it allows you to create a small visual studio project so that you can track scripts as well as check them in. Cheers, Grant Grant Castner Phone: 0458 770 749 Twitter: https://twitter.com/grantcastner LinkedIn: au.linkedin.com/pub/grant-castner

Re: Sql Server Patch Scripts

We use SQL Server projects for patching, version controlled with git. For schema changes, we run a compare on the project and the dev database (assuming that is where the schema changes are) and create an upgrade script from that. For actual data changes to be applied, we create separate scripts

Re: Sql Server Patch Scripts

I do this as well with projects. It works well if you only have to deploy to a couple of databases. If you have many databases (>3) then I find the migrations approach described by Grant works very well. On Mon, Nov 2, 2015 at 3:15 PM, David Burstin wrote: > We use SQL

Re: Sql Server Patch Scripts

I have previously used FlyWay to perform database migrations, and in fact there is even a course on Pluralsight for this. I am currently generating scripts via Visual Studio Database Projects, but there appear to be a few problems with this. Firstly, it doesn't seem to scale well. It seems ok