Visual Studio Team Edition for DB Professionals

Historically, we have always been focused on improving the individual developer productivity with every release of VS.  When we introduced Visual Studio Team System (VSTS) as part of Visual Studio 2005 late last year, we expanded our focus to significantly enhance software team productivity with an integrated set of tools that enable team members to work together in a collaborative fashion.  We are now ready to take the next big step forward in that evolution.


I’m excited to announce today a new addition to the VSTS family – Visual Studio Team Edition for Database Professionals.


Visual Studio Team Edition for Database Professionals is a great example of the innovation we are bringing to the application lifecycle management (ALM) market.  It’s a market-shifting database development product designed to manage database changes, improve software quality through database testing and bring the benefits of Visual Studio Team System and life cycle development to the database professional (such as database architects, database developers and database administrators).


You can find out more about it and get access to early community technology previews here.


We’re making Visual Studio Team Edition for Database Professionals part of the Visual Studio Team Suite, so you’ll get this product for free when we RTM this edition if you are a Visual Studio Team Suite subscriber through MSDN. 


We’re in the midst of planning for the next version of Visual Studio Team System and I’ll post more details as we make more progress.  Meanwhile, I hope you enjoy the CTP (to be released at TechEd the week of June 11th) and look forward to your feedback on this product.



Comments (16)

  1. Cathal says:

    the links broken or not live yet, probably the latter as I had a quick look about the team system developer center and can’t see any mention of it there either.


  2. Somasegar just announced on his blog Visual Studio Team Edition for DB Professionals:

    Visual Studio…

  3. Somasegar says:

    Hi – I just checked the link again and it seemed to work and go to the right place.  The URL is:

    – somasegar

  4. Today Soma has announced that we’ve extended the Visual Studio Team Edition range to include an edition…

  5. Microsoft officially announced the newest flavor of the Visual Studio Team Edition Suite.  Visual…

  6. Thanks!!!”> auto site insurance. [URL=]home insurance[/URL]: The autos insurance company, compare car insurance, auto insurance. Also [url=]cars insurance[/url] from website .

  7. Hi! auto site insurance. The autos insurance company, compare car insurance, auto insurance. from website .

  8. Tobi says:

    Downloaded this today and i’ll be using this from now as there is nothing out there that can do integrated DB change management iside the VS IDE. This is going to be a big plus for us.

    I have imported a schema and checked it into source control to see if we’d have any problems using Sourcegear’s Vault and it’s worked flawlessly so far.

    A couple of problems I did have is when comparing a Database (Source) to a Project (Target) how do you actually update the project?

    Ther other was creating a unit test. It couldn’t find DBUnitTest.vstemplate. (but I’m thinking this may be becuase i’m running professional version of VS.NET 2005)

    A couple of suggestions. We have a team of people who develop and test with their own copy of tyhe DB, once a month when we build all changes are compared against a current model and the changes are gathered one at a time. Now this take time and we use tools such as  DBGhost and Apex SQL, Redgate etc to gather the changes but it’s still time consuming when you have say 6 or 7 DB’s to sync. I have always thought an automated system that would collect and log changes against a model and build an update script, create a new db model and upgrade all the source databases to the current version would save a great deal of time for our build manager.

    Also the ability scan the DB and solution source code and find out if there are any broken dependancies to tables and fields / stored procedure that may suggest that certain things have fallen out of use or into disrepair which can happen over time in large code bases.

    So far it looks excellent, can’t wait to start looking at the unit testing & refactoring side.



  9. camerons says:

    Hello Tobi!

    I’m Cameron Skinner, the team leader for DB Professionals. I noticed your comment on Soma’s blog, and wanted to jump in here.

    In regards to the couple of problems you are experiencing. In the current bits, we have disabled the ability to synchronize between a database ( source ) and a project ( target ), but are planning on having that functionality in place by the time we ship by the end of the year, so please hang in there!

    For the .template problem, try the following:

    Assuming you have C# or VB.NET installed, open up a VS command prompt ( Start->Programs->Microsoft Visual Studio 2005->Visual Studio Tools->Visual Studio 2005 Command Prompt ) and then type in the following command:

    devenv.exe /setup

    Hope that helps! In the meantime, let me make sure you are aware of the team forum site ( ) as well as my blog, where I’m also glad to answer any comments ( ).

    Hope that helps!


  10. padmakar says:


    I was trying to import the database schema from an sql server database.  I was getting the following error while doing this

    An error has occured while establishing a connection to the server.  When connecting to sql server 2005, this failure may be caused by the fact under the default settings SQL server does not allow remote connections. (provider:SQL network interfaces, error: 26 – Error locating Server/Instance Specified).

    Even the target database is on a remote server and we are able to access the databases in the server using sql server management studio.  Is it mandatory that we need to have sql server express or developer edition on the pc where we have this visual studio team edition for db professionals?



  11. Mairead (Microsoft) says:

    Hi Padmakar

    Let me see if I can help you with the Importing database issue.

    First off, you need to have a local instance of SQL Server (express or dev edition or greater) installed locally, this allows us to do some additional design time validation of the sql syntax.

    The error you are experiencing may be a result of misconfigurations of DBPro to use that local SQL instance and may be manifesting itself through the Import  Database Schema process.

    Can you ensure you have the following set up correctly

    If above does not resolve your issue, please ping me directly so that we can troubleshoot further