{"id":4824,"date":"2007-10-15T16:24:00","date_gmt":"2007-10-15T16:24:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2007\/10\/15\/sql-database-publishing-wizard-is-now-in-visual-studio-2008\/"},"modified":"2007-10-15T16:24:00","modified_gmt":"2007-10-15T16:24:00","slug":"sql-database-publishing-wizard-is-now-in-visual-studio-2008","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/sql-database-publishing-wizard-is-now-in-visual-studio-2008\/","title":{"rendered":"SQL Database Publishing wizard is now in Visual Studio 2008."},"content":{"rendered":"

The SQL database publishing wizard is a very popular web-downloadable add-in for Visual Studio 2005. The publishing wizard addresses the issue where a developer needs to deploy a local database from his development machine to a hosting environment on a remote machine. <\/SPAN>We received a lot of positive feedback for this wizard and we decided to integrate this with Visual Studio 2008. This is a feature that was added post Beta2 and will be available with Visual Studio 2008 RTM.<\/SPAN><\/FONT><\/FONT><\/P>\n

 <\/FONT><\/SPAN><\/P>\n

The wizard supports two key database hosting deployment scenarios:<\/FONT><\/FONT><\/SPAN><\/P>\n

 <\/FONT><\/SPAN><\/P>\n

1.<\/FONT>      <\/SPAN><\/SPAN><\/SPAN><\/I><\/B>It generates a single .SQL script file which can be used to recreate a database on a remote machine<\/FONT><\/I><\/B><\/FONT><\/P>\n

Using the Database Publishing Wizard  you can point to a database on your local machine, and then automatically create a .SQL script file that contains the setup logic needed to re-create a replica of the database on any remote system – for example an external hosting system. This .SQL script includes everything needed to create the database schema (tables, views, sprocs, triggers, full-text catalogs, roles, rules, etc). You also have the option of populating the new database with the same data contents as your local tables. Most hosters today support the upload and running of .SQL files to their hosted environments using their admin control panels. So, all you need to do is upload and run the .SQL script generated by the Database Publishing Wizard, and you will have a working database in your hosted environment. This should considerably reduce the effort required to deploy your databases.<\/FONT><\/FONT><\/SPAN><\/P>\n

2.<\/FONT>      <\/SPAN><\/SPAN><\/SPAN><\/I><\/B>It connects to a web service provided by your hoster and directly creates objects on a specified hosted database.<\/FONT><\/I><\/B><\/FONT><\/P>\n

 <\/FONT><\/P>\n

The Database Publishing Wizard also enables you to point at a database you are working with on your local system, and then use web-services to transfer and recreate the database in your remote hoster environment (without you having to create the .SQL file or use the hoster admin control panel to run it).  This publishing option does require that a SQL Publishing web-service be exposed in the hosting environment, and the SQL Server Hosting Toolkit includes a free implementation of this SQL Publishing web-service that we’ll be working with hosters to aggressively deploy<\/FONT><\/P>\n

 <\/FONT><\/SPAN><\/P>\n

The release version of <\/FONT><\/SPAN> Visual Studio 2008 will come pre-installed with the 1.2 version of SQL Publishing Wizard.<\/FONT><\/FONT><\/SPAN><\/P>\n

 <\/SPAN><\/P>\n

So now that you know what the Database Publishing wizard does, let us dig deeper into how it will work with Visual Studio 2008.<\/FONT><\/FONT><\/SPAN><\/P>\n

 <\/FONT><\/P>\n

Step 1: <\/B>Create a new website by selecting menu File ->New Web Site. <\/B>Switch to Server Explorer and add a new Data connection and connect to a database. In this case we will use the Northwind database that comes with SQL Express. You should point to the database you want to publish.<\/FONT><\/FONT><\/P>\n

 <\/FONT><\/P>\n

Step 2: <\/B>Select Northwind.dbo node in Server explorer and right click to bring up the context menu. In the Context menu you have a \u201cPublish to provider\u2026\u201d option.<\/FONT><\/FONT><\/P>\n

<\/FONT> <\/P>\n

<\/P>\n

<\/FONT> <\/P>\n

Step 3: <\/B>Click  <\/SPAN>\u201cPublish to provider \u2026\u201d to launch the Database Publishing Wizard.<\/FONT><\/FONT><\/P>\n

<\/FONT> <\/P>\n

<\/P>\n

<\/FONT><\/FONT> <\/P>\n

Step 4: <\/B>Click Next to select the mode. Let us go with \u201cScript to file\u201d mode. We will need to specify the .SQL file name and location.<\/P>\n

 <\/P>\n

<\/P>\n

 <\/P>\n

Step 5: <\/B>Click Next and you will get to the Publishing Options. On this page, select the script for target database (SQL Server 2000 or SQL Server 2005) and the types of data to publish (Schema, Data or Schema+Data). You also have the option to drop existing object in script if you want to.<\/P>\n

 <\/P>\n

<\/P>\n

 <\/B><\/P>\n

Step 6: <\/STRONG>Keep the default selection and hit next and generate the .SQL script.<\/P>\n

 <\/P>\n

Step 7: <\/B>The .SQL file  <\/SPAN>generated contains a script that you can run on any SQL server to re-create all the tables, sprocs, views, triggers, full-text catalogs, etc. for a database, as well as import and add all of the table row data that was in the database at the time the .SQL file was created. <\/SPAN><\/P>\n

 <\/P>\n

Step 8: <\/B>The .SQL file is a plain text file. You can open it in your favorite editor and customize it as you need. <\/P>\n

 <\/P>\n

Step 9: <\/B>Now that we have our .SQL files, we can go about using them to install our database at our hoster. Exactly how to install the .SQL files will vary depending on how the hoster give access to our SQL account.  Some hosters provide an HTML based file-upload tool that allows you to provide a .SQL file – which they will then execute against the SQL database you own.  <\/P>\n

Other hosters provide an online query tool (like below) that allows you to copy\/paste SQL statements to run against your database.  If you have a hoster which provides an online query tool like this, then you can open the .SQL file with a text-editor and copy\/paste the contents into the query textbox and run it.<\/P>\n

 <\/P><\/FONT><\/FONT>\n

 <\/FONT><\/B><\/P>\n

And that is all there is to using the Database Publishing Wizard. Hope this feature is useful to you.<\/FONT><\/P>\n

 <\/FONT><\/P>\n

Scott Guthrie also has a nice blog entry on this. You can read it  <\/SPAN><\/FONT><\/FONT>here<\/FONT><\/A>.<\/FONT><\/P>\n

<\/EM><\/FONT><\/FONT> <\/P>\n

~ Reshmi Mangalore<\/EM><\/FONT><\/FONT><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"

The SQL database publishing wizard is a very popular web-downloadable add-in for Visual Studio 2005. The publishing wizard addresses the issue where a developer needs to deploy a local database from his development machine to a hosting environment on a remote machine. We received a lot of positive feedback for this wizard and we decided […]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[7265,31,7262,7273,147,7267,7264,7268],"class_list":["post-4824","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-announcements","tag-asp-net","tag-development","tag-orcas","tag-visual-studio","tag-vwd","tag-wap","tag-web"],"acf":[],"blog_post_summary":"

The SQL database publishing wizard is a very popular web-downloadable add-in for Visual Studio 2005. The publishing wizard addresses the issue where a developer needs to deploy a local database from his development machine to a hosting environment on a remote machine. We received a lot of positive feedback for this wizard and we decided […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=4824"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4824\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=4824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=4824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=4824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}