September 2012 Entries
The goal here is to use SSDT SqlPackage to deploy the output of a Visual Studio 2012 Database project… a bit in the same fashion that was detailed here : http://geekswithblogs.net/8... The difference is we want to do it on an environment where Visual Studio 2012 and SSDT are not installed. This might be the case of your Production server. Package structure So, to get started you need to create a folder named “DeploymentSSDTRedistributa... ......
For our continuous integration needs, we use a powershell script to handle deployment. A simpler approach would be to have a deployment task embedded within the build process. See the solution provided here by Jakob Ehn (a most interesting read which also dives into the '”deploying from Visual Studio” specifics) : http://geekswithblogs.net/j... For our needs, though, clearly separating our build phase from our deployment phase is important. ......
With Visual Studio 2012 and the use of SSDT technology, there is only one type of database project : SQL Server Database Project. With Visual Studio 2010, we used to have SQL Server 2008 Server Project which we used to define server-level objects, mostly logins and linked servers. A convenient wizard allowed for creation of this type of projects. It does not exists anymore. Here is how to create an equivalent of the SQL Server 2008 Server Project with Visual Studio 2012: Create a new SQL Server Database ......
Visual Studio 2012 introduces a change regarding Database Projects : they now use the SSDT technology, which means old VS2010 database projects (VSDB projects) need to be converted. Hopefully, VS2012 does that for you and it is quite painless, but in my case some unnecessary artifacts from the old project were left in place. Also, when reopening the solution, database projects appeared unconverted even if I had converted them in the previous session and saved the solution. Converting the project(s) ......
At the office, we extensively use VS2010 SQL Server 2008 Database Projects and SQL Server 2008 Server Projects in our Visual Studio 2010 solutions. With Visual Studio 2012, those types of projects are replaced by the SQL Server Database Project using the SSDT (SQL Server Data Tools) technology. I started investigating the shift from Visual Studio 2010 to Visual Studio 2012 and specifically what needs to be done concerning those database projects in terms of painless migration, continuous integration ......