Re: Using RoundhousE for existing database with data

[Andy]

If you put your current scripts into the "after create" folder (I forget the exact name), they will be run if RH creates your database during migration.  If RH doesn't create the db, that folder is ignored.

Does that solve the issue?

On Friday, February 8, 2013 2:17:54 PM UTC-6, Jayme Edwards wrote:

Folks,

I just used RoundhousE on a project where we had a new database, and started from the ground up. I'm now at a client where we have databases that already exist and I'm wondering how best to start using RoundhousE.

I can generate a script with the initial schema of the database, and put that in the "up" folder so it gets created correctly in my dev environment (which gets dropped during each build and recreated), but in production I won't want that to run since it's already at that version.

Any advice? Should I insert the version numbers into the RoundhousE schema tables in prod?

Thanks!

Jayme

[Alan Howard]

Sounds like Andy has a possible solution. You can also use SQL Baseline/Powerup to generate the initial set of create scripts for your database (I prefer their format and content over what SSMS will produce), run them on dev, and then script out the resulting data from the Roundhouse tables and apply to prod (and anywhere else you don't want the scripts to run). 

On 9 February 2013 09:17, Jayme Edwards <jayme....@gmail.com> wrote:

Folks,

I just used RoundhousE on a project where we had a new database, and started from the ground up. I'm now at a client where we have databases that already exist and I'm wondering how best to start using RoundhousE.

I can generate a script with the initial schema of the database, and put that in the "up" folder so it gets created correctly in my dev environment (which gets dropped during each build and recreated), but in production I won't want that to run since it's already at that version.

Any advice? Should I insert the version numbers into the RoundhousE schema tables in prod?

Thanks!

Jayme

--
You received this message because you are subscribed to the Google Groups "chucknorris" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chucknorrisframe...@googlegroups.com.
To post to this group, send email to chucknorri...@googlegroups.com.
Visit this group at http://groups.google.com/group/chucknorrisframework?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jayme Edwards]

OK this makes sense. If I understand correctly, I can basically script out production and put this script in "after create". I can use the up folder as normal to create migrations. The initial script will only run in dev where the database gets dropped each time. I restore production to test/UAT before running migrations there.

Thanks guys!

Jayme

On Saturday, February 9, 2013 10:45:34 PM UTC-6, nzduck wrote:

Sounds like Andy has a possible solution. You can also use SQL Baseline/Powerup to generate the initial set of create scripts for your database (I prefer their format and content over what SSMS will produce), run them on dev, and then script out the resulting data from the Roundhouse tables and apply to prod (and anywhere else you don't want the scripts to run). 

On 9 February 2013 09:17, Jayme Edwards <jayme....@gmail.com> wrote:

Folks,

I just used RoundhousE on a project where we had a new database, and started from the ground up. I'm now at a client where we have databases that already exist and I'm wondering how best to start using RoundhousE.

I can generate a script with the initial schema of the database, and put that in the "up" folder so it gets created correctly in my dev environment (which gets dropped during each build and recreated), but in production I won't want that to run since it's already at that version.

Any advice? Should I insert the version numbers into the RoundhousE schema tables in prod?

Thanks!

Jayme

--
You received this message because you are subscribed to the Google Groups "chucknorris" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chucknorrisframework+unsub...@googlegroups.com.