#Visual studio 2012 data tools full version#
#Visual studio 2012 data tools upgrade#

Now I thought I’d try and build the solution against my local machine (SQL Server 2008 R2 instance) and the first problem I found was that in our 2010 solution we have.

#Visual studio 2012 data tools full version#

This allows you to do stuff on an instance of SQL Server without having to install the full version of SQL Server. This is a SQL Server Express instance (I believe) and whenever you do a debug build and publish (or hit F5) the solution will get deployed to this instance. In “SQL Server” you will see a connection to “(localdb)”. You’ll see you have two nodes: “SQL Server” which is used to connect to various SQL Servers and “Projects” which replaces “Schema View” and shows the objects in each of the projects in the solution. In SSDT you now get more in the “SQL Server Object Explorer” window.

I also noticed that there was no “Schema View”. publish.xml file was created in each of the databases for each of the configurations that we have in our project (more on these files further on). sqlproj files being created to replace the original. I converted them all and the solution opened in VS 2012.ĭoing this resulted in new.

#Visual studio 2012 data tools upgrade#

As I’d already said “No” to the upgrade I wasn’t shown the upgrade wizard window again but I was shown a window that had a list of the existing DB projects with a checkbox asking which ones I wanted to convert. I thought I’d play about with the conversion wizard so I took a copy of our development branch and opened it in VS 2012. I was able to use the solution in 2010 as before. Please note that there is a note under this option that says “You will not be prompted to convert these projects again”. As I was not ready to do the conversion I chose “No”. There were two options available: “Yes, convert to SQL Server Database Projects” and “No, do not convert”. Once I’d installed SSDT for 2010 the next time I opened our DB solution (in VS 2010) the “Convert To SQL Server Database Project” wizard was displayed. The Dec 2012 release of SSDT for VS 2010 can be found here: This would allow people to choose whether they want to use VS 2010 or 2012 once the solution had been upgraded.

To make the upgrade process as easy as possible it was suggested that all the members of the DB team deploy SSDT for Visual Studio 2010. Please note, this is still a work in progress and we have not yet completed the upgrade. I’ve been playing about with it and this is what I’ve found so far. The developers working on the API are already using Visual Studio 2012 and the DB team (of which I am a part) are looking to upgrade our Visual Studio 2010 database projects to use SQL Server Data Tools (SSDT) in Visual Studio 2012. I’m currently working on a project that is replacing a suite of legacy applications (SQL Server 2008 R2 and ASP.NET) with a REST API with an underlying SQL Server 2008 R2 database.