Oracle Support Announced for VS DB Pro 2010

Quest Software has announced that they will be creating an Oracle DSP (Database Schema Provider) for Visual Studio Team System 2010.  This means that all if you have Oracle databases in your apps you can get the same benefits from the Database Edition.

Quest has opened up a Beta program on their TeamFuze.net site for Oracle professionals using Team System.

Advertisements

Data Dude + Developer Edition = Team Developer

{From My VSTS KB}

In today’s press release titled: "Visual Studio 2010 and .NET Framework 4.0 Overview" MS also announced the merge of the Developer Edition and Database Edition SKU’s.

From Gert’s post:

What does this mean?

In the next release of Visual Studio Team System we will be merging the feature sets of the Development Edition and the Database Edition into a single product. The new product – part of Visual Studio Team System codename “Rosario” – will include all of the features in the Development Edition and the Database Edition as well as new capabilities delivering even more value in a single product. This will provide a more complete set of capabilities for building software in today’s data-driven environments. Bringing these two feature sets together enables you to take advantage of the core tools for application development as well as the necessary tools for database development, including performance profiling, code analysis, code metrics, code coverage, database refactoring, Schema Compare, Data Compare, and more.

As an MSDN subscriber we want you to realize the benefit of this merged feature set now, which is why we are extending this exclusive offer. If you have either the Visual Studio Team System 2008 Development Edition with MSDN Premium subscription or the Visual Studio Team System 2008 Database Edition with MSDN Premium subscription, on October 1, 2008 you will have access to both the Development Edition and Database Edition through MSDN Subscriber Downloads. This change also applies to customers who purchased Visual Studio 2005 Team Edition for Software Developers with MSDN Premium Subscription and Visual Studio 2005 Team Edition for Database Professionals with MSDN Premium Subscription.

Data Dude + Developer Edition = Team Developer

In today’s press release titled: “Visual Studio 2010 and .NET Framework 4.0 Overview” MS also announced the merge of the Developer Edition and Database Edition SKU’s.

From Gert’s post:

What does this mean?

In the next release of Visual Studio Team System we will be merging the feature sets of the Development Edition and the Database Edition into a single product. The new product – part of Visual Studio Team System codename “Rosario” – will include all of the features in the Development Edition and the Database Edition as well as new capabilities delivering even more value in a single product. This will provide a more complete set of capabilities for building software in today’s data-driven environments. Bringing these two feature sets together enables you to take advantage of the core tools for application development as well as the necessary tools for database development, including performance profiling, code analysis, code metrics, code coverage, database refactoring, Schema Compare, Data Compare, and more.

As an MSDN subscriber we want you to realize the benefit of this merged feature set now, which is why we are extending this exclusive offer. If you have either the Visual Studio Team System 2008 Development Edition with MSDN Premium subscription or the Visual Studio Team System 2008 Database Edition with MSDN Premium subscription, on October 1, 2008 you will have access to both the Development Edition and Database Edition through MSDN Subscriber Downloads. This change also applies to customers who purchased Visual Studio 2005 Team Edition for Software Developers with MSDN Premium Subscription and Visual Studio 2005 Team Edition for Database Professionals with MSDN Premium Subscription.

Data Dude:Deploy Action On CTP16 Does Not Deploy The Database To Target

A lot of users confused and don’t understand why the database does not appear on the target server when they do deploy.

The reason is that in CTP 16, the default deploy mechanism is to deploy to script. If you want to deploy to database you have to change the ‘Deploy action’ on the project properties, deploy tab to ‘Create a deployment script (.sql) and deploy to the database.’

deploy

Data Dude On RadioTFS

Just published over on Radio TFS a special episode on the Database Edition of Team System with the Data Dude man – Gert Drapers.  In the show Gert talks how the product got started, where it is now, where it is going in the future, the latest CTP of the Database Edition GDR and more.

VSTSDB 2008 GDR CTP16

Gert just posted about the release of CTP16 of the Visual Studio Team System 2008 Database Edition GDR release.

From Gert’s post:

This release adds the following features:

  • VSDBCMD.EXE
    • We added independent commandline deployment and reverse engineer, which can be used on machines that do not have Visual Studio installed, in order to deploy the results of a database project build (.dbschema file), or if you need to generate a .dbschema file so you can for example compare it, this commandline tool will let you do that as well.
  • Database Project (.dbproj) Upgrades
    • CTP15 enabled upgrade of project files, but did not included updating Data Generation Plans (.DGEN files), which now be upgraded when they are opened the first time inside the DGEN designer.
  • Schema Compare
    • You can now choose the SQL Command Variables (SQLCMD) to use during a Schema Compare session by clicking the “Specify SQLCMD variables” button on the Schema Compare toolbar. This will allow you to compare projects that are using SQLCMD variables and provide the contextual information via the variable values.
    • You can now set the Schema Compare options at the session level, in addition to Tools->Options, by clicking the Settings button on the Schema Compare toolbar.
    • And you can now save your Schema Compare session and reopen it again. We also added an item template for this, name “Schema Comparison”
  • Extensibility
    • We finished the namespace and assembly naming cleanup. As a result all assembly names and namespaces have been changed. This means if you have code leveraging our extensibility mechanisms you need to update the assembly references and namespaces in your code.
    • We added the ability to add your own refactoring types! So now you can create your own refactoring command and have it change all the required references inside the schema. This is above and beyond the ability to create your own refactoring targets (the sources your want to change by an refactoring type), static code analysis rules, data generators, data distributions and test conditions.
    • We now also offer public access to our TSQL parsers for SQL Server 2000, 2005 and 2008, including the script generator functionality.
  • And then there are many more enhancements in the parser, interpreter, validation, build and deploy.

Pre-requisites:

CTP16 requires the following components to be installed:

Download location:

You can download CTP16 from the following location:

NOTE: If you have a previous version of the GDR installed, you will have to first uninstall this and then install the latest CTP16 bits.

VSTSDB 2008 GDR CTP16

Gert just posted about the release of CTP16 of the Visual Studio Team System 2008 Database Edition GDR release.

From Gert’s post:

This release adds the following features:

  • VSDBCMD.EXE
    • We added independent commandline deployment and reverse engineer, which can be used on machines that do not have Visual Studio installed, in order to deploy the results of a database project build (.dbschema file), or if you need to generate a .dbschema file so you can for example compare it, this commandline tool will let you do that as well.
  • Database Project (.dbproj) Upgrades
    • CTP15 enabled upgrade of project files, but did not included updating Data Generation Plans (.DGEN files), which now be upgraded when they are opened the first time inside the DGEN designer.
  • Schema Compare
    • You can now choose the SQL Command Variables (SQLCMD) to use during a Schema Compare session by clicking the “Specify SQLCMD variables” button on the Schema Compare toolbar. This will allow you to compare projects that are using SQLCMD variables and provide the contextual information via the variable values.
    • You can now set the Schema Compare options at the session level, in addition to Tools->Options, by clicking the Settings button on the Schema Compare toolbar.
    • And you can now save your Schema Compare session and reopen it again. We also added an item template for this, name "Schema Comparison"
  • Extensibility
    • We finished the namespace and assembly naming cleanup. As a result all assembly names and namespaces have been changed. This means if you have code leveraging our extensibility mechanisms you need to update the assembly references and namespaces in your code.
    • We added the ability to add your own refactoring types! So now you can create your own refactoring command and have it change all the required references inside the schema. This is above and beyond the ability to create your own refactoring targets (the sources your want to change by an refactoring type), static code analysis rules, data generators, data distributions and test conditions.
    • We now also offer public access to our TSQL parsers for SQL Server 2000, 2005 and 2008, including the script generator functionality.
  • And then there are many more enhancements in the parser, interpreter, validation, build and deploy.

Pre-requisites:

CTP16 requires the following components to be installed:

Download location:

You can download CTP16 from the following location:

NOTE: If you have a previous version of the GDR installed, you will have to first uninstall this and then install the latest CTP16 bits.

%d bloggers like this: