Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a database project that goes through iterations (only one so far) and I need to deploy a testing version to a live server. I’m not sure how to go about this.
I can make all the changes in a copy and then remake those changes in the live version. That doesn’t make sense.
Is there a way to change a server name to an existing server? What’s the best practice for this scenario?
With a Visual Studio Database Project, you should be able to have as many database connections defined as you like. When you go run your scripts, you can pick an menu option called “Run On….” and then pick which server connection to run those scripts on.
Just make sure the database name is the same for both instances, or make sure that you do not specify
USE (database)at the top of all your scripts, if the database names are different from target to target.