Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

chucknorris/roundhouse

RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control

People

Repo info

Activity

Rob Reynolds

@ferventcoder

that would be helpful

Simon Timms

@stimms

let me see if I can pull a release notes together today

Rob Reynolds

@ferventcoder

Simon Timms

@stimms

how do you get the down scripts to run?

Rob Reynolds

@ferventcoder

there are no down scripts

it was a thought but ultimately it hasn’t been found to be needed

as with all things there are several ways to handle issues

from restoring a backup to just running another script

Simon Timms

@stimms

ah, okay

I have a weird scenario where I have multiple schemas and each schema as its own separate set of up scripts

so dropping the whole database, as I typically do, means you have to go to a bunch of projects to get back to a desired state

This is totally our fault

Rob Reynolds

@ferventcoder

so do you have a prod backup?

scrubbed or whatever

Simon Timms

@stimms

nope, we build a test database from scripts and environment specific test data scripts

really these things should be different databases but operational issues are a limiting facotr

factor

Rob Reynolds

@ferventcoder

I’ll provide a tiny bit of advice first

Simon Timms

@stimms

I can work around this - it isn't a common enough problem that I'd expect roundhouse to support it

oh, please do

Rob Reynolds

@ferventcoder

if you want to get the best benefit of RH, it’s best to switch to RestoreRun mode after you’ve deployed to production

and deploy all the way up through your environments with RH

once you’ve hit prod, restorerun from a backup (scrubbed/schema only with some items) is going to give you the most protection from some developer changing a script that has already run on prod

and will subsequently fail your prod deploy

https://github.com/chucknorris/roundhouse/wiki/RoundhousEModes#our-application-is-now-used-in-production

I just updated the wiki page

Simon Timms

@stimms

I think that's a reasonable approach

our build pipeline does include a stage where rh would be run against a production backup

so we will catch it but perhaps further down the pipe that would be ideal

Rob Reynolds

@ferventcoder

once you are in restore run, you want it to work all the way back to local dev

I just added the use case for restore run

also https://www.nuget.org/packages/roundhouse.refreshdatabase.ef/

and https://www.nuget.org/packages/roundhouse.refreshdatabase.fnh/

Rob Reynolds

@ferventcoder

but you could also just use the refresh database stuff in your local Visual Studio without a migrations framework

it’s super handy

https://github.com/chucknorris/roundhouse/wiki/RoundhouseRefreshDatabaseEF

https://github.com/chucknorris/roundhouse/wiki/Roundhouserefreshdatabasefnh

Simon Timms

@stimms

Talked it over with the team and we're going to alter our processes to be more what you suggest, thanks for the tips

Rob Reynolds

@ferventcoder

are you already using the refreshdatabase visual studio project console?

I remember asking @drusellers why we needed it at first

and once I saw it, I was like OMG how did I ever live without this?

Simon Timms

@stimms

we probably won't use that we don't make use of a fully featured ORM just Dapper

so our RH scripts are pretty much the source of truth

Rob Reynolds

@ferventcoder

Yeah, we didn’t start it with a migrations framework

it was simply something that just took the sql files and applied them

So while I would be tweaking a sql file, I could quickly rerun anything that hadn’t yet been run against the prod database because it would just restore the prod backup and apply all new scripts

so a new script could be continually changed until it was pushed up

xdfrancis

@xdfrancis