post deploy script to add permissions not in production

cennis

I have a post deploy script for each non-production environment. These scripts create users and add permissions for folks like QA. We have these as post deploy scripts because we don't want the permissions to exist in production.

What is the best way to execute a .sql script that is in the current DB repository as a last step? Right now, I am playing around with using RGPublish to publish the .sql file to a directory on the target machine and then a Powershell script to execute the .sql file. Am I making this more complicated than it needs to be?

Chris.Allen

I would say that the best way to run a sql query when you need to (as opposed to when DM does it) is to use sqlcmd within the powershells script.

You can then run any arbitrary sql script post-deploy.