Deploying SQL Database changes from a SSDT project

3
votes

I have a Visual Studio SSDT project which I use to keep track of all database changes and it is all kept under source control.

From Visual Studio I can deploy this to my local SQL Server and also our test environment. However I can not remotely connect to our Production SQL Server for security reasons but I can RDP into the production server.

What is the best way to ensure all my database changes get deployed to production?

Not sure it makes much difference for this question but I am using VS 2015 and SQL Server 2012.

1
sql-serverdeploymentsql-server-data-tools
I think you will need access to production environment, otherwise how else you expect to deploy these changes to that environment. As far as "security" is concerned, you have perfectly valid reason to have access to prod environment, I would suggest you to speak to your dba. - M.Ali

1 Answers

7
votes

You can generate a DACPAC on the production environment and then copy that DACPAC over to your development environment. From there, you can use SSDT to compare what is in source control with what is in the DACPAC and generate DDL scripts that will bring your production database in sync with source control.