This works fine in our environment now since we have more flexibility in where we check out the code in our repository. As long as we follow the naming convention you have suggested we can run the scripts against production to create/update the affected objects for the version.

Michael, it sounds like you are bending over backwards to make the app operate nicely for shops that 1) Only use root folders for schema names 2) Use folder names that match production schema names but not dev/qa and 3) Aren't interested in running scripts on anything but production. This seems like an extremely narrow subset of customers you are catering too. I suggest you make the schema name in the script match the schema name in the database and then create a separate migration feature that could do schema name translation.

I think if you fix this http://redgate.uservoice.com/forums/174014-oracle-tools/suggestions/3652032-allow-source-control-in-sub-folders-of-repository then it will make this work better in our environment.

Neil did you make progress on this one?

Hi Curtis,

Thanks for this. I'll have a look into it today and be in touch.

Neil

Update on this, it appears that this is the case in all scripts NOT just the UserObjectPrivs folder. Let me know if you need anymore information.