Update: Thomas Murphy from the VSTS4DB dev team has informed me that the correct project type to use is Database Projects-->Microsoft SQL Server-->SQL Server XXXX which is different to one of the screenshots below which uses Other project Types-->Database-->Database project.
Update 2: Cameron Skinner has more information on the project structure here: https://blogs.msdn.com/camerons/archive/2006/06/13/629069.aspx
On the train whilst making my way into work this morning I took a first look at Visual Studio Team System for Database Professionals (catchy title!!!) and thought I'd share my early experiences here. Its only really screenshots at the moment but it helped to give myself a quick feel of the product so perhaps it will do for you too.
I wanted to test out the new schema compare functionality which is probably the feature here that I'm looking forward to the most.
I started from my standard Visual Studio install and went for "New project...". I hadn't spotted anywhere in the docs I'd read which project type I should go for so opted for "Database project..." which I don't remember seeing before.
Upon clicking OK I got prompted to add a database reference.
I'd never seen this before so was fairly confident I had selected the right thing. So far so good!
Upon entering VS proper I took a look at Solution Explorer proper and saw some stuff that looked like it probably came out of VSTS4DB
But where to next? AHA...there's some new menu items. This looks promising
I went for "Data->Schema Compare->New Schema Comparison..." and got the following dialog prompting me for my source and target:
Clicked OK and off it went and generated the change script to make my target look like my source.
OK cool. Now we're seeing something interesting. Top left you can see "87 objects compared". It took about 10 seconds which is acceptable so no problems with performance here.
I'm given the option of creating or skipping an object and you'll have to trust me that selecting 'Skip' automatically changes the script in the bottom portion of the screen.
After that I select "Export to Editor" at the top of the screen and my script appears in a standard sql window
It all looks pretty good I think. That is seemingly simple functionality that DB developers have been crying out for for years.
More to come from me in the coming few weeks hopefully but in the meantime here's a few links that might help:
Go and get stuck in. I certainly can't wait to get headlong into this new product!
-Jamie