How do I Publish my Microsoft SQL server database


In order to publish your database to your hosting package, you need to use the SQL database publishing wizard.

http://www.microsoft.com/downloads/details.aspx?familyid=56E5B1C5-BF17-42E0-A410-371A838E570A&displaylang=en


Download from the url above, and install on your local machine.


Run this from the start menu and go through the options to select your local database using Windows Authentication.

Follow the options from here to Script your database to file and save the file to your local machine.


Once you have this, open SQL management studio,

http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&displaylang=en

Enter your new Database details


Server Hostname: 
Your db user name
your db password.

Once connected, find your database in the list and right click, then select New Query.


Then find your scripted .sql file and open this using notepad. Select All the contents and Copy. Then paste this into the Query window In SQL management studio.


Then click Execute from the icons at the top of the screen.


This will then populate your remote database with the content of your local database.


Once complete, change your connection string to reflect the following:


Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Connection Strings

We're often asked how to create a connection string to a database.  In fact a variety of...

SQL Enterprise Manager reports 'no items'

Run this script in query analyzer against the master db ===================copy everything below...

SQL Object Ownership script

DECLARE @objname nvarchar(517),@DynSQL nvarchar(4000) DECLARE obj_cursor CURSOR FORSELECT name...

SQL db shrink code

--Select Count(name) from sysdatabases declare @db as varchar(100)set @db = 'db to be shrunk...

Why can't I connect to the SQL server using Enterprise Manager/Management Studio

SQL Enterprise Manager tries, by default, to connect via Named Pipes. As this cannot run across...