0

I have a DB project in Visual Studio and I need to deploy it to a remote system as a pre-packaged script (or similar) as a new database.

The Publish option will generate a .publish SQL script but only if you supply a connection first, and the script includes machine-local information e.g. logging paths.

I want something I can copy onto the DB-server machine running SSMS and it will create the DB. What is the proper way to do this, I see I also have DAC and DLL files emitted during build.

1 Answer 1

1

What is the proper way to do this?

Connect to a server that doesn't have any version of your database, and publish. Publish calculates an incremental deployment, so it needs to see the current state of the target SQL Server.

Sign up to request clarification or add additional context in comments.

3 Comments

I cannot connect to the server. I need to produce something I can transfer to a separate system. It doesn't have to be SQL scripts but that's all I'm familiar with. Is that what all this DAC/DLLs are for?
Publish to a local SQL Server to generate the script.
Sorry I misread you there that makes more sense.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.