Home of the Data Dude : VSDBPro

More Team Developer + Data Edition Merge Information

gertd — Fri, 03 Oct 2008 07:25:55 GMT

Per October 1st 2008 MSDN subscribers who own or buy a new Visual Studio Team System Developer license are entitled to also install the Visual Studio Team System Database Edition, and MSDN subscribers who own or buy a new Visual Studio Team System Database Edition license are entitled to install the Visual Studio Team System Developer Edition. This is the immediate benefit for current owners of the two SKU's merging in the upcoming Visual Studio Team System codename "Rosario" version.

Based on this announcement we received many questions, seeking clarification, in this post I will try to answer the six most common questions.

The first place to go visit is the FAQ page covering the Dev+Data merge on MSDN, please see http://msdn.microsoft.com/en-us/vsts2008/products/cc990295.aspx

Additional FAQ:

Q: Exactly which Visual Studio versions covered as part of the this program?

A: If you own one of the following licenses:

You currently have:	You are entitled to install:
Visual Studio 2005 Team Edition for Software Developers with MSDN Premium Subscription	Visual Studio 2005 Team Edition for Database Professionals
Visual Studio 2005 Team Edition for Database Professionals with MSDN Premium Subscription	Visual Studio 2005 Team Edition for Software Developers
Visual Studio Team System 2008 Development Edition with MSDN Premium Subscription	Visual Studio Team System 2008 Database Edition
Visual Studio Team System 2008 Database Edition with MSDN Premium Subscription	Visual Studio Team System 2008 Development Edition

Q: We are a Microsoft partner and received our Visual Studio Team Development Edition license through the Microsoft Partner ISV Program or Microsoft Partner CDS Program?

A: This change will also applies to the licenses of Visual Studio Team System Development Edition that Microsoft partners received through the Microsoft Partner ISV and CDS Program’s.

Q: Do I need to re-install or un-install my existing Edition before installing the new additional Edition?

A: No, this is not needed, the Editions install in an additive fashion; you can install in the Developer Edition after the Database Edition or the other way around.

Q: I have Visual Studio 2008 SP1 installed, after I installed the new Edition, do I have to re-install Visual Studio 2008 SP1?

A: Yes, after installing additional features you need to re-install SP1 to update the new binaries installed.

Q: I have Visual Studio 2005 SP1 installed, after I installed the new Edition, do I have to re-install Visual Studio 2005 SP1?

A: Yes, after installing additional features you need to re-install SP1 to update the new binaries installed. Also Visual Studio 2005 Team Edition for Database Professionals prerequisites that Visual Studio 2005 SP1 is installed before installing the Visual Studio 2005 Team Edition for Database Professionals.

Q: How does the Visual Studio Team System 2008 Database Edition GDR fit in to this?

A: The Visual Studio Team System 2008 Database Edition GDR version only installs on top of the Visual Studio Team System 2008 Database Edition release. So if you first have to install the Visual Studio Team System 2008 Database Edition, then install Visual Studio 2008 SP1 which is a prerequisite of the GDR and then install the GDR release.

I hope this helps,
-GertD

Team Developer + Team Data = Team Developer!

gertd — Tue, 30 Sep 2008 01:06:22 GMT

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

Better Together – Visual Studio Team System Development Edition and Database Edition
In recognition of the increased need to integrate more of the lifecycle members together, we will provide a unified Development and Database product in Visual Studio Team System 2010. Beginning October 1, 2008 Development Edition and Database Edition MSDN subscribers will have access to both products.

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.

-GertD

Trace Helper

gertd — Mon, 18 Aug 2008 01:16:44 GMT

This is the last part of the 3 part diagnostics series. This part will introduce you to a little helper utility that I wrote to make configuring the diagnostics and tracing options a lot simpler and more accessible. As discussed in the previous two blog posts in this series: Diagnosing Problems and Event Monitor everything is controlled from the Registry. Enabling and disabling tracing, the event monitor and determining what and where to trace to, all of this is controlled by Registry settings.

Hence the reason why created a small HTML Application that will allow you set change the settings through a simply user interface.

The end result looks like this:

You can download this utility from my DataDude SkyDrive, there is a specific version for each major release.

Each link points to a .ZIP file that contains a simple .HTA file. Simply launch the .HTA file and it will start a browser session with the UI shown above.

NOTE: Make sure to restart Visual Studio after you made change to your trace settings!

This concludes the 3 part diagnostics series, I hope this was useful.

-GertD

Event Monitor

gertd — Sun, 17 Aug 2008 23:49:08 GMT

In part 2 of diagnosing problems I want to introduce you to an other build-in diagnostics tools that we might ask you to run with tracking down problems, the "event monitor". The event monitor is one of those tools that we use during development of the product for troubleshooting problems during development.

Enabling the Event Monitor

Since by default the event monitor is turned off we first need to enable it, by switch a bit in the Registry. Depending on which version you are using you need to do this in a different Registry location:

Visual Studio Team Edition for Database Professionals (2005)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\DBPro]
"ShowEventMonitor"=dword:00000001

Visual Studio Team System 2008 Database Edition

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\DBPro]
"ShowEventMonitor"=dword:00000001

Visual Studio Team System 2008 Database Edition GDR

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\VSTSDB]
"ShowEventMonitor"=dword:00000001

NOTE: After you change the Registry setting you need to close down Visual Studio and restart it!

Launching the Event Monitor

Now that we enable the use of the event monitor we can now launch it. You first need to create or open a "Database Project" (.dbproj) since the Event Monitor is only in the context of a Database Project.

Right click on the Database project node inside Solution Explorer, this will bring up a context menu. The first entry in the context menu is the event monitor. Note that the exact text of the menu entry can be different per version. In the GDR release it is named "VSTSDB Event Monitor".

When you select the menu entry a tool window will appear with the same name as the menu entry.

Using the Event Monitor

Now that we have the event monitor launched lets use it.

Let's go through each icon in the toolbar first to explore the options.

Clear - this options deletes all captured events from the display window and the internal buffer.

Capture - this is a toggle that will turn on and off capturing of events.

Filter - this will bring up a dialog where you can select the events to capture.

The events to capture are:

Dump Schema Manager - this option dumps the content of the internal schema manager. This is all the information about the schema objects and there relationships.

Example output of Dump Schema Manager:

        1: (1:36:18 PM) 

       2: (1:36:18 PM) ---------------------------------------

       3: (1:36:18 PM)    Schema Context Dump : Database4

       4: (1:36:18 PM) ---------------------------------------

       5: (1:36:18 PM)        Sql Schema Manager : 

       6: (1:36:18 PM)            Disallows Server Objects.

       7: (1:36:18 PM)            Allows User Objects.

       8: (1:36:18 PM)            Collation: Latin1_General_CS_AS

       9: (1:36:18 PM) 

(1:36:18 PM)        Start Custom Data : Database4

(1:36:18 PM)        Custom Data #0

(1:36:18 PM)            Category=ModelCapability

(1:36:18 PM)            DataType=

(1:36:18 PM)            'ModelCapability'='Default'

(1:36:18 PM)        Custom Data #1

(1:36:18 PM)            Category=AnsiNulls

(1:36:18 PM)            DataType=

(1:36:18 PM)            'AnsiNulls'='True'

(1:36:18 PM)        Custom Data #2

(1:36:18 PM)            Category=QuotedIdentifier

(1:36:18 PM)            DataType=

(1:36:18 PM)            'QuotedIdentifier'='True'

(1:36:18 PM)        Custom Data #3

(1:36:18 PM)            Category=DeploymentCollation

(1:36:18 PM)            DataType=

(1:36:18 PM)            'DeploymentCollation'='SQL_Latin1_General_CP1_CS_AS'

(1:36:18 PM)        Custom Data #4

(1:36:18 PM)            Category=CompatibilityMode

(1:36:18 PM)            DataType=

(1:36:18 PM)            'CompatibilityMode'='100'

(1:36:18 PM)        Custom Data #5

(1:36:18 PM)            Category=Reference

(1:36:18 PM)            DataType=DbSchema

(1:36:18 PM)            'FileName'='C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 9.0\VSTSDB\EXTENSIONS\SQLSERVER\2008\DBSCHEMAS\MICROSOFT.SQLTYPES.DBSCHEMA'

(1:36:18 PM)            'LogicalName'='Microsoft.SqlTypes.dbschema'

(1:36:18 PM)        End Custom Data : Database4

(1:36:18 PM) 

(1:36:18 PM)        Start External Elements : Database4

(1:36:18 PM)        ElementClass = 'ISql100DatabaseOptions', Name = '<unnamed>'

(1:36:18 PM)        ElementClass = 'ISql100Filegroup', Name = '[PRIMARY]'

(1:36:18 PM)        ElementClass = 'ISql100Queue', Name = '[dbo].[EventNotificationErrorsQueue]'

(1:36:18 PM)        ElementClass = 'ISql100Queue', Name = '[dbo].[QueryNotificationErrorsQueue]'

(1:36:18 PM)        ElementClass = 'ISql100Queue', Name = '[dbo].[ServiceBrokerQueue]'

(1:36:18 PM)        ElementClass = 'ISql100Service', Name = '[http://schemas.microsoft.com/SQL/Notifications/EventNotificationService]'

(1:36:18 PM)        ElementClass = 'ISql100Service', Name = '[http://schemas.microsoft.com/SQL/Notifications/QueryNotificationService]'

(1:36:18 PM)        ElementClass = 'ISql100Service', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceBroker]'

(1:36:18 PM)        ElementClass = 'ISql90Assembly', Name = '[Microsoft.SqlServer.Types]'

(1:36:18 PM)        ElementClass = 'ISql90AssemblySource', Name = '<unnamed>'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[DEFAULT]'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[http://schemas.microsoft.com/SQL/Notifications/PostEventNotification]'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification]'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice]'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceDiagnostic]'

(1:36:18 PM)        ElementClass = 'ISql90Contract', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceEcho]'

(1:36:18 PM)        ElementClass = 'ISql90Endpoint', Name = '[Dedicated Admin Connection]'

(1:36:18 PM)        ElementClass = 'ISql90Endpoint', Name = '[TSQL Default TCP]'

(1:36:18 PM)        ElementClass = 'ISql90Endpoint', Name = '[TSQL Default VIA]'

(1:36:18 PM)        ElementClass = 'ISql90Endpoint', Name = '[TSQL Local Machine]'

(1:36:18 PM)        ElementClass = 'ISql90Endpoint', Name = '[TSQL Named Pipes]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[DEFAULT]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/Notifications/EventNotification]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/Notifications/QueryNotification]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/FailedRemoteServiceBinding]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/FailedRoute]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRemoteServiceBinding]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/BrokerConfigurationNotice/MissingRoute]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/EndDialog]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/Error]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceDiagnostic/Description]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceDiagnostic/Query]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceDiagnostic/Status]'

(1:36:18 PM)        ElementClass = 'ISql90MessageType', Name = '[http://schemas.microsoft.com/SQL/ServiceBroker/ServiceEcho/Echo]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_accessadmin]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_backupoperator]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_datareader]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_datawriter]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_ddladmin]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_denydatareader]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_denydatawriter]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_owner]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[db_securityadmin]'

(1:36:18 PM)        ElementClass = 'ISql90Role', Name = '[public]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_accessadmin]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_backupoperator]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_datareader]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_datawriter]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_ddladmin]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_denydatareader]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_denydatawriter]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_owner]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[db_securityadmin]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[dbo]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[guest]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[INFORMATION_SCHEMA]'

(1:36:18 PM)        ElementClass = 'ISql90Schema', Name = '[sys]'

(1:36:18 PM)        ElementClass = 'ISql90User', Name = '[dbo]'

(1:36:18 PM)        ElementClass = 'ISql90User', Name = '[guest]'

(1:36:18 PM)        ElementClass = 'ISql90User', Name = '[INFORMATION_SCHEMA]'

(1:36:18 PM)        ElementClass = 'ISql90User', Name = '[sys]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedDataType', Name = '[sys].[sysname]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[geography]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[geometry]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[hierarchyid]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[sys].[geography]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[sys].[geometry]'

(1:36:18 PM)        ElementClass = 'ISql90UserDefinedType', Name = '[sys].[hierarchyid]'

(1:36:18 PM)        ElementClass = 'ISqlBuiltInType', Name = '[bigint]'

(1:36:18 PM)        ElementClass = 'ISqlBuiltInType', Name = '[binary]'

(1:36:18 PM)        ElementClass = 'ISqlBuiltInType', Name = '[bit]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[char]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[cursor]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[date]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[datetime]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[datetime2]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[datetimeoffset]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[decimal]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[float]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[image]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[int]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[money]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[nchar]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[ntext]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[numeric]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[nvarchar]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[real]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[smalldatetime]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[smallint]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[smallmoney]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[sql_variant]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[table]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[text]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[time]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[timestamp]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[tinyint]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[uniqueidentifier]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[varbinary]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[varchar]'

(1:36:19 PM)        ElementClass = 'ISqlBuiltInType', Name = '[xml]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[bulkadmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[dbcreator]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[diskadmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[processadmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[public]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[securityadmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[serveradmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[setupadmin]'

(1:36:19 PM)        ElementClass = 'ISqlServerRole', Name = '[sysadmin]'

(1:36:19 PM)        End External Elements : Database4

(1:36:19 PM) 

   <?xml version="1.0" encoding="utf-16"?>

   <SchemaManager DspName="Microsoft.Data.Schema.Sql.SqlDsp.Sql100DatabaseSchemaProvider" Collation="Latin1_General_CS_AS">

     <Header>

       <CustomData Category="ModelCapability">

         <Metadata Name="ModelCapability" Value="Default" />

       </CustomData>

       <CustomData Category="AnsiNulls">

         <Metadata Name="AnsiNulls" Value="True" />

       </CustomData>

       <CustomData Category="QuotedIdentifier">

         <Metadata Name="QuotedIdentifier" Value="True" />

       </CustomData>

       <CustomData Category="DeploymentCollation">

         <Metadata Name="DeploymentCollation" Value="SQL_Latin1_General_CP1_CS_AS" />

       </CustomData>

       <CustomData Category="CompatibilityMode">

         <Metadata Name="CompatibilityMode" Value="100" />

       </CustomData>

       <CustomData Category="Reference" Type="DbSchema">

         <Metadata Name="FileName" Value="C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 9.0\VSTSDB\EXTENSIONS\SQLSERVER\2008\DBSCHEMAS\MICROSOFT.SQLTYPES.DBSCHEMA" />

         <Metadata Name="LogicalName" Value="Microsoft.SqlTypes.dbschema" />

       </CustomData>

     </Header>

     <Model>

       <Element Type="ISql100DatabaseOptions">

         <Property Name="Collation" Value="SQL_Latin1_General_CP1_CS_AS" />

         <Property Name="IsAnsiNullDefaultOn" Value="True" />

         <Property Name="IsAnsiNullsOn" Value="True" />

         <Property Name="IsAnsiPaddingOn" Value="True" />

         <Property Name="IsAnsiWarningsOn" Value="True" />

         <Property Name="IsArithAbortOn" Value="True" />

         <Property Name="IsConcatNullYieldsNullOn" Value="True" />

         <Property Name="IsAutoCreateStatisticsOn" Value="True" />

         <Property Name="IsAutoUpdateStatisticsOn" Value="True" />

         <Property Name="RecoveryMode" Value="3" />

         <Property Name="IsFullTextEnabled" Value="True" />

         <Property Name="IsAutoUpdateStatisticsAsyncOn" Value="True" />

         <Property Name="PageVerifyMode" Value="3" />

         <Property Name="MirroringPartnerServer" Value="" />

         <Property Name="IsPartnerServerRedoQueueUnlimited" Value="True" />

         <Property Name="MirroringPartnerServerTimeout" Value="10" />

         <Property Name="MirroringWitnessServer" Value="" />

         <Property Name="ServiceBrokerOption" Value="2" />

         <Property Name="ParameterizationOption" Value="1" />

         <Property Name="CompatibilityMode" Value="100" />

         <Relationship Name="DefaultFilegroup">

           <Entry>

             <References ExternalSource="BuiltIns" Name="[PRIMARY]" />

           </Entry>

         </Relationship>

       </Element>

     </Model>

   </SchemaManager>

(1:36:19 PM) ---------------------------------------

(1:36:19 PM)

Dump Project System - this option will dump all the file names and objects that are in the project system

Example output of Dump Project System:

       1: (1:35:35 PM) ---------------------------------------

       2: (1:35:35 PM)   Project System Dump : Database4

       3: (1:35:35 PM) ---------------------------------------

       4: (1:35:35 PM)      DatabaseProjectNode State :c:\demo\Database4\Database4.dbproj

       5: (1:35:35 PM)      DBProItemIdMap ->

       6: (1:35:35 PM)          _idToNodeList ->

       7: (1:35:35 PM)              1, References

       8: (1:35:35 PM)              2, c:\Program Files (x86)\Microsoft Visual Studio 9.0\VSTSDB\Extensions\SqlServer\2008\DBSchemas\Microsoft.SqlTypes.dbschema

       9: (1:35:35 PM)              3, c:\demo\Database4\Properties

(1:35:35 PM)              4, c:\demo\Database4\Properties\Database.sqlsettings

(1:35:35 PM)              5, c:\demo\Database4\Properties\Database.sqldeployment

(1:35:35 PM)              6, c:\demo\Database4\Properties\Database.sqlcmdvars

(1:35:35 PM)              7, c:\demo\Database4\Scripts

(1:35:35 PM)              8, c:\demo\Database4\Scripts\Pre-Deployment

(1:35:35 PM)              9, c:\demo\Database4\Scripts\Pre-Deployment\Script.PreDeployment.sql

(1:35:35 PM)              10, c:\demo\Database4\Scripts\Post-Deployment

(1:35:35 PM)              11, c:\demo\Database4\Scripts\Post-Deployment\Script.PostDeployment.sql

(1:35:35 PM)              12, c:\demo\Database4\Schema Objects

(1:35:35 PM)              13, c:\demo\Database4\Schema Objects\Database Level Objects

(1:35:35 PM)              14, c:\demo\Database4\Schema Objects\Database Level Objects\Assemblies

(1:35:35 PM)              15, c:\demo\Database4\Schema Objects\Database Level Objects\Database Triggers

(1:35:35 PM)              16, c:\demo\Database4\Schema Objects\Database Level Objects\Security

(1:35:35 PM)              17, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Asymmetric Keys

(1:35:35 PM)              18, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Certificates

(1:35:35 PM)              19, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Audit Specification

(1:35:35 PM)              20, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Encryption Keys

(1:35:35 PM)              21, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Master Keys

(1:35:35 PM)              22, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles

(1:35:35 PM)              23, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Application Roles

(1:35:35 PM)              24, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Database Roles

(1:35:35 PM)              25, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Schemas

(1:35:35 PM)              26, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Signatures

(1:35:35 PM)              27, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Symmetric Keys

(1:35:35 PM)              28, c:\demo\Database4\Schema Objects\Database Level Objects\Security\Users

(1:35:35 PM)              29, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker

(1:35:35 PM)              30, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Broker Priorities

(1:35:35 PM)              31, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Contracts

(1:35:35 PM)              32, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Event Notifications

(1:35:35 PM)              33, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Message Types

(1:35:35 PM)              34, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Queues

(1:35:35 PM)              35, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Remote Service Binding

(1:35:35 PM)              36, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Routes

(1:35:35 PM)              37, c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Services

(1:35:35 PM)              38, c:\demo\Database4\Schema Objects\Database Level Objects\Storage

(1:35:35 PM)              39, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Filegroups

(1:35:35 PM)              40, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Files

(1:35:35 PM)              41, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Catalogs

(1:35:35 PM)              42, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Stoplists

(1:35:35 PM)              43, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Functions

(1:35:35 PM)              44, c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Schemes

(1:35:35 PM)              45, c:\demo\Database4\Schema Objects\Schemas

(1:35:35 PM)              46, c:\demo\Database4\Schema Objects\Schemas\dbo

(1:35:35 PM)              47, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability

(1:35:35 PM)              48, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Defaults

(1:35:35 PM)              49, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Functions

(1:35:35 PM)              50, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Rules

(1:35:35 PM)              51, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Stored Procedures

(1:35:35 PM)              52, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types

(1:35:35 PM)              53, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Data Types

(1:35:35 PM)              54, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Table Types

(1:35:35 PM)              55, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Types CLR

(1:35:35 PM)              56, c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\XML Schema Collections

(1:35:35 PM)              57, c:\demo\Database4\Schema Objects\Schemas\dbo\Synonyms

(1:35:35 PM)              58, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables

(1:35:35 PM)              59, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Constraints

(1:35:35 PM)              60, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Indexes

(1:35:35 PM)              61, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Keys

(1:35:35 PM)              62, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Statistics

(1:35:35 PM)              63, c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Triggers

(1:35:35 PM)              64, c:\demo\Database4\Schema Objects\Schemas\dbo\Views

(1:35:35 PM)              65, c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Indexes

(1:35:35 PM)              66, c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Statistics

(1:35:35 PM)              67, c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Triggers

(1:35:35 PM)              68, c:\demo\Database4\Data Generation Plans

(1:35:35 PM)          _folderNodes ->

(1:35:35 PM)              c:\demo\Database4\Properties

(1:35:35 PM)              c:\demo\Database4\Scripts

(1:35:35 PM)              c:\demo\Database4\Scripts\Pre-Deployment

(1:35:35 PM)              c:\demo\Database4\Scripts\Post-Deployment

(1:35:35 PM)              c:\demo\Database4\Schema Objects

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Assemblies

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Database Triggers

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Asymmetric Keys

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Certificates

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Audit Specification

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Encryption Keys

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Master Keys

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Application Roles

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Database Roles

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Schemas

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Signatures

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Symmetric Keys

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Users

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Broker Priorities

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Contracts

(1:35:35 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Event Notifications

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Message Types

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Queues

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Remote Service Binding

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Routes

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Services

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Filegroups

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Files

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Catalogs

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Stoplists

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Functions

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Schemes

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Defaults

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Functions

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Rules

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Stored Procedures

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Data Types

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Table Types

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Types CLR

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\XML Schema Collections

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Synonyms

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Constraints

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Indexes

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Keys

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Statistics

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Triggers

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Indexes

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Statistics

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Triggers

(1:35:36 PM)              c:\demo\Database4\Data Generation Plans

(1:35:36 PM)          _urlToNodeList ->

(1:35:36 PM)              c:\demo\Database4\Properties, 3

(1:35:36 PM)              c:\demo\Database4\Properties\Database.sqlsettings, 4

(1:35:36 PM)              c:\demo\Database4\Properties\Database.sqldeployment, 5

(1:35:36 PM)              c:\demo\Database4\Properties\Database.sqlcmdvars, 6

(1:35:36 PM)              c:\demo\Database4\Scripts, 7

(1:35:36 PM)              c:\demo\Database4\Scripts\Pre-Deployment, 8

(1:35:36 PM)              c:\demo\Database4\Scripts\Pre-Deployment\Script.PreDeployment.sql, 9

(1:35:36 PM)              c:\demo\Database4\Scripts\Post-Deployment, 10

(1:35:36 PM)              c:\demo\Database4\Scripts\Post-Deployment\Script.PostDeployment.sql, 11

(1:35:36 PM)              c:\demo\Database4\Schema Objects, 12

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects, 13

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Assemblies, 14

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Database Triggers, 15

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security, 16

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Asymmetric Keys, 17

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Certificates, 18

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Audit Specification, 19

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Database Encryption Keys, 20

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Master Keys, 21

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles, 22

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Application Roles, 23

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Roles\Database Roles, 24

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Schemas, 25

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Signatures, 26

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Symmetric Keys, 27

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Security\Users, 28

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker, 29

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Broker Priorities, 30

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Contracts, 31

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Event Notifications, 32

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Message Types, 33

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Queues, 34

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Remote Service Binding, 35

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Routes, 36

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Service Broker\Services, 37

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage, 38

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Filegroups, 39

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Files, 40

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Catalogs, 41

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Full Text Stoplists, 42

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Functions, 43

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Database Level Objects\Storage\Partition Schemes, 44

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas, 45

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo, 46

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability, 47

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Defaults, 48

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Functions, 49

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Rules, 50

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Stored Procedures, 51

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types, 52

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Data Types, 53

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Table Types, 54

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\User Defined Types CLR, 55

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Programmability\Types\XML Schema Collections, 56

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Synonyms, 57

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables, 58

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Constraints, 59

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Indexes, 60

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Keys, 61

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Statistics, 62

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Tables\Triggers, 63

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views, 64

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Indexes, 65

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Statistics, 66

(1:35:36 PM)              c:\demo\Database4\Schema Objects\Schemas\dbo\Views\Triggers, 67

(1:35:36 PM)              c:\demo\Database4\Data Generation Plans, 68

(1:35:36 PM)          _urlsToEvaluate ->

(1:35:36 PM)      ProjectConfigs ->

(1:35:36 PM)         Key Output for config Release is c:\demo\Database4\obj\Release\Database4.dbschema

(1:35:36 PM)         All Outputs -->

(1:35:36 PM)            c:\demo\Database4\obj\Release\Database4.dbschema

(1:35:36 PM)         Key Output for config Debug is c:\demo\Database4\obj\Debug\Database4.dbschema

(1:35:36 PM)         All Outputs -->

(1:35:36 PM)            c:\demo\Database4\obj\Debug\Database4.dbschema

(1:35:36 PM)         Catalog Properties:

(1:35:36 PM)         AllowSnapshotIsolation,False

(1:35:36 PM)         AnsiNullDefault,True

(1:35:36 PM)         AnsiNulls,True

(1:35:36 PM)         AnsiPadding,True

(1:35:36 PM)         AnsiWarnings,True

(1:35:36 PM)         ArithAbort,True

(1:35:36 PM)         AutoClose,False

(1:35:36 PM)         AutoCreateStatistics,True

(1:35:36 PM)         AutoShrink,False

(1:35:36 PM)         AutoUpdateStatistics,True

(1:35:36 PM)         AutoUpdateStatisticsAsynchronously,True

(1:35:36 PM)         ChangeTrackingRetentionPeriod,2

(1:35:36 PM)         ChangeTrackingRetentionUnit,Days

(1:35:36 PM)         CloseCursorOnCommitEnabled,False

(1:35:36 PM)         ConcatNullYieldsNull,True

(1:35:36 PM)         DatabaseAccess,MULTI_USER

(1:35:36 PM)         DatabaseChaining,False

(1:35:36 PM)         DatabaseState,ONLINE

(1:35:36 PM)         DateCorrelationOptimizationOn,False

(1:35:36 PM)         DefaultCollation,SQL_Latin1_General_CP1_CS_AS

(1:35:36 PM)         DefaultCursor,LOCAL

(1:35:36 PM)         DefaultFilegroup,PRIMARY

(1:35:36 PM)         DefaultFileStreamFilegroup,

(1:35:36 PM)         EnableFullTextSearch,True

(1:35:36 PM)         ForcingServiceAllowDataLoss,False

(1:35:36 PM)         IsChangeTrackingAutoCleanupOn,True

(1:35:37 PM)         IsChangeTrackingOn,False

(1:35:37 PM)         IsEncryptionOn,False

(1:35:37 PM)         MirroringPartnerServer,

(1:35:37 PM)         MirroringPartnerServerTimeout,10

(1:35:37 PM)         MirroringWitnessOn,False

(1:35:37 PM)         MirroringWitnessServer,

(1:35:37 PM)         NumericRoundAbort,False

(1:35:37 PM)         PageVerify,NONE

(1:35:37 PM)         Parameterization,SIMPLE

(1:35:37 PM)         PartnerServerFailover,False

(1:35:37 PM)         PartnerServerOff,False

(1:35:37 PM)         PartnerServerRedoQueueSize,

(1:35:37 PM)         PartnerServerRedoQueueUnlimited,True

(1:35:37 PM)         PartnerServerResumed,False

(1:35:37 PM)         PartnerServerSafetyOff,False

(1:35:37 PM)         PartnerServerSuspended,False

(1:35:37 PM)         QuotedIdentifier,True

(1:35:37 PM)         ReadCommittedSnapshot,False

(1:35:37 PM)         Recovery,FULL

(1:35:37 PM)         RecursiveTriggersEnabled,False

(1:35:37 PM)         RollbackMode,DoNotScript

(1:35:37 PM)         ServiceBrokerOption,DisableBroker

(1:35:37 PM)         SupplementalLoggingOn,False

(1:35:37 PM)         TornPageDetection,False

(1:35:37 PM)         Trustworthy,False

(1:35:37 PM)         UpdateOptions,READ_WRITE

(1:35:37 PM)         VardecimalStorageFormatOn,False

(1:35:37 PM)         Server Properties:

(1:35:37 PM) ---------------------------------------

(1:35:37 PM)

Dump RDT (Running Document Table) - this option dumps the content of the Visual Studio Running Document Table for the active Database Project.

Example output of Dump RDT

(1:46:03 PM) ---------------------------------------
(1:46:03 PM)   Dumping RDT :
(1:46:03 PM)   c:\demo\Database4\Database4.dbproj
(1:46:03 PM)   c:\demo\Database4\Database4.sln
(1:46:03 PM) ---------------------------------------

Dump GC (Garbage Collector) - this option dumps the details of the garbage collector for the process.

Example output of Dump GC

(1:34:21 PM) Dump GC Started...
(1:34:21 PM) Total memory: 5698376
(1:34:21 PM) Max generation: 2
(1:34:21 PM) Collection count Gen0: 28
(1:34:21 PM) Collection count Gen1: 7
(1:34:21 PM) Collection count Gen2: 2
(1:34:21 PM) Dump GC Ended...

Start GC Collection - this options force a garbage collection run, trying to trim down the memory consumption

Example output of Start GC Collection

(1:47:15 PM) GC Collection Started...
(1:47:15 PM) Total memory: 5862760
(1:47:15 PM) GC.Collect(0)...
(1:47:15 PM) Total memory: 4166892
(1:47:15 PM) GC.Collect(1)...
(1:47:15 PM) Total memory: 4150808
(1:47:15 PM) GC.Collect(2)...
(1:47:15 PM) Total memory: 3931476
(1:47:15 PM) GC Collection Ended...

Save to File - this option save the captured events to a text file.

This concludes part 2 of the diagnostics series, one more to go!

-GertD

Tech·Ed 2008 Developers

gertd — Thu, 29 May 2008 23:10:33 GMT

In case you are coming to the Developer edition of Tech·Ed next week, we have a lot of exiting things for you. As you can see below there are many sessions, hosted in both the developer and database tracks. Breakout sessions, chalk talks, panel discussions and hands-on lab, all covering Visual Studio Team System Database Edition.

It all starts in BillG his keynote, where Brian Harry will show some of the partner work we have been involved in, stay tuned for more details on that!

Besides all the sessions you will be able to talk to the team members 1-1 on the booth. We have a presence in the Visual Studio Team System area and we are also present on the SQL Server booth to demonstrate the integration with SQL Server 2008.

We hope to see you at Tech·Ed,

-GertD

Session list:

Date	Session Title
Tuesday, June 3 1:15 PM - 2:30 PM	DVP310 Agile Database Development (level 300)
Tuesday, June 3 3:00 PM - 4:15 PM	TLA310 End-to-End Database Development Using Microsoft Visual Studio Team System 2008 Database Edition (level 300)
Thursday, June 5 10:15 AM - 11:30 AM	DAT326 Supporting Microsoft SQL Server 2008 within Microsoft Visual Studio Team System Database Edition (level 300)
Thursday, June 5 1:00 PM - 2:15 PM	DAT01-TLC Managing Database References in Microsoft Visual Studio Team System 2008 Database Edition (level 400)
Thursday, June 5 3:00 PM - 4:00 PM	TEO Panel _25 Testing the SQL Database (panel discussion)
Thursday, June 5 4:30 PM - 5:45 PM	DAT02-TLC Microsoft Visual Studio Team System 2008 Database Edition: Integrating Database Developers in Your Software Management Life Cycle (level 200)
Friday, June 6 8:30 AM - 9:45 AM, S230 A	TLA320 The Microsoft Visual Studio Team System Database Project Ecosystem: Integrating ALM and Database Tools via Extensibility (level 300)
Friday, June 6 10:15 AM - 11:30 AM	DAT03-TLC Customization of Data Generation Using Microsoft Visual Studio Team System 2008 Database Edition (level 400)

Sessions details:

DVP310 Agile Database Development (level 300)

Tuesday, June 3 1:15 PM - 2:30 PM, S330 C

Speaker(s): Richard Hundhausen

Session Type: Breakout Session

Agile remains a popular buzzword these days. Some teams strive to become more agile, while others tend to avoid it. Where do you weigh in? Regardless, it's not something that has traditionally been applicable to SQL Server database development, until recently. With the proper configuration and use of Microsoft Visual Studio Team System Team Foundation Server and the Database Editions tools, it is possible to satisfy your clients' changing needs should they extend to the database.

TLA310 End-to-End Database Development Using Microsoft Visual Studio Team System 2008 Database Edition (level 300)

Tuesday, June 3 3:00 PM - 4:15 PM, S330 A

Speaker(s): Mairead O'Donovan

Session Type: Breakout Session

The Database Edition of Visual Studio Team System 2008 provides a comprehensive set of tools and features that integrates the Database Development Lifecycle into the overall Application Development Lifecycle. In this session, we cover the principles that tie the Database Development model into the larger ALM, and take a tour through the features of the Database Edition with an emphasis on how each leg of the Lifecycle is supported by Database-specific tools and features. Special attention is paid to the enhancements added as part of the VSTS 2008 release, as well as the extended functionality added when you install the optional Database Edition Power Tools. This session is a mix of theory and practice, with live demonstrations of the fundamental features found at each level of the Database Development Lifecycle.

DAT326 Supporting Microsoft SQL Server 2008 within Microsoft Visual Studio Team System Database Edition (level 300)

Thursday, June 5 10:15 AM - 11:30 AM, S230 E (DEV)

Speaker(s): Gert Drapers, Jamie Laflen

Session Type: Breakout Session

One of the most anticipated aspects of the upcoming Database Edition for Visual Studio Team System release, code name "Rosario", is the support for SQL Server 2008. This session covers how the new architecture, features, and functionality of the new Visual Studio Team System Database Edition version will enable the support of SQL Server 2008 new data types, new syntax and other functionality. In addition, this session provides an overview of all the new functionality which applies to SQL Server 2000, 2005, and 2008.

DAT01-TLC Managing Database References in Microsoft Visual Studio Team System 2008 Database Edition (level 400)

Thursday, June 5 1:00 PM - 2:15 PM, Green Theater 1

Speaker(s): Gert Drapers, Jamie Laflen

Session Type: Interactive Theaters

Visual Studio Team System 2008 Database Edition enhances the ability of the Database Project to understand and manage database references across multiple databases from within a single project, or across several projects. This chalk talk focuses on how best to best manage three- and four-part name references inside a Visual Studio Team System Database Edition project.

TEO Panel _25 Testing the SQL Database (panel discussion)

Thursday, June 5 3:00 PM - 4:00 PM

Speaker(s): Gert Drapers, Jamie Laflen, Adam Machanic, David Reed, John Welch

Session Type: TechEd Online Sessions

It goes almost without saying that testing is a core aspect of any properly structured software development effort. Yet when it comes to the database layer, we often see developers shy away from a proper testing regimen. The prevailing attitude is often that database testing is either not necessary or simply too difficult to properly accomplish. But the truth is, database testing is just as doable, and certainly just as valuable, as testing of any other layer. In this panel we will discuss why you want to test your database, and the various types of database testing that you should be doing as you develop and deploy your application. We will cover testing scenarios to handle functionality, regression, performance, scalability, and other key metrics as they relate to your database infrastructure. Without testing, your database's runtime behaviors are effectively an unknown. Come to this panel to learn how not to leave things to chance.

DAT02-TLC Microsoft Visual Studio Team System 2008 Database Edition: Integrating Database Developers in Your Software Management Life Cycle (level 200)

Thursday, June 5 4:30 PM - 5:45 PM, Green Theater 1

Speaker(s): Brian Randell

Session Type: Interactive Theaters

For many applications, the database is the foundation. Yet for many teams, the “database professional” has limped along without the tools necessary to do their job. Managing database change and evolution is critical to successful software projects. In this session, learn how Visual Studio Team Edition for Database Professionals can help you integrate database design, creation, and evolution in your overall software development life cycle using the entire Team System. Learn how the product integrates with other team editions and team members including features such as source code control, work item tracking, test case management, and build.

TLA320 The Microsoft Visual Studio Team System Database Project Ecosystem: Integrating ALM and Database Tools via Extensibility (level 300)

Friday, June 6 8:30 AM - 9:45 AM, S230 A

Speaker(s): Gert Drapers, Brent Gross (IBM Corp.)

Session Type: Breakout Session

Discover how Visual Studio Team System code name "Rosario": Database Edition empowers developers to actively participate in, and bring agility to, the database development process. If you work with databases, you will want see how the features offered by the latest addition to Visual Studio Team System (VSTS) integrate the database developer into the Application Development Lifecycle. This exciting product is changing the way database developers work with databases forever, by moving the "One Version of the Truth" for database schema from the production server into source control. This presentation focuses on extending the "Rosario" release of Database Edition to enable non SQL Server databases to plug into the VSTS Database Edition platform. Now database developers can manage their database schema changes for Microsoft SQL Server databases as well as non SQL Server databases within the same environment. In addition to enabling an extension platform for non SQL Server databases, learn also how the Visual Studio Team System code name "Rosario": Database Edition has enabled a database development tools extensibility platform for third-party companies to plug in additional database development tools into the VSTS Database Edition product.

DAT03-TLC Customization of Data Generation Using Microsoft Visual Studio Team System 2008 Database Edition (level 400)

Friday, June 6 10:15 AM - 11:30 AM, Green Theater 1

Speaker(s): Jamie Laflen

Session Type: Interactive Theaters

Are the data generators that ship with Visual Studio not meeting your needs? Do you need to generate data from outside the development environment? This talk drills into making the most of the 2008 data generation API to answer these and other questions.

MSDB Reference Projects

gertd — Wed, 30 Apr 2008 08:50:12 GMT

The reference projects needed to resolve objects that reside inside an MSDB database have been posted on the MSDN Code Gallery site.

You can find them on: http://code.msdn.microsoft.com/dbpromsdbsamples

We did not post .dbmeta files but stub projects, because .dbmeta files require the collation to match with your environment. This would result in a multitude of files do download. So instead we provided projects, you do need to make sure you set the project collation to match with your own environment. After you have done this you can create your own .dbmeta file if you do not want to reference a project.

NOTE: Since the projects are a stub projects, in other words the content of objects like procedure have been removed, you cannot and should not use these project to deploy to your msdb database!

-GertD

VSDB 2005 Service Release 1 Roll-up Package 1 (KB941278)

gertd — Wed, 12 Mar 2008 04:36:46 GMT

Visual Studio 2005 Team System Database Professional post Service Release 1 (SR1) roll-up package 1, is now available.

For a list of issues that are fixed, please see knowledge base article KB941278.

You can download the roll-up from the Microsoft Connect site at:
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=11229

-GertD

Database Compatibility Level

gertd — Sun, 17 Feb 2008 08:33:00 GMT

VSTS-DB, both the 2005 and 2008 version, makes an assumption with regards to database compatibility levels, which can cause problems in certain use cases.

The assumption is that the DesignDB instance used for validation of the schema inside the project is set to a 80 compatibility level when using a SQL Server 2000 project and to 90 when you are using a SQL Server 2005 project. If you have a database schema that was migrated from SQL Server 2000 to 2005 and is relying on the fact that the database compatibility level must be set to 80 to keep your code running, this will cause TSD4001 errors when you import/open that schema in to a SQL Server 2005 project and ultimately prevent you from building and deploying your project, since TSD4xxxx are always errors, which come from the DesignDB instance.

Lets look at two common cases that some of you have reported that cause problems:

Problem description	SQL Server 2000 sp_dbcmptlevel = 80	SQL Server 2005 sp_dbcmptlevel = 80	SQL Server 2005 sp_dbcmptlevel = 90
Using hints without a WITH clause, for example: CREATE VIEW [dbo].[v_test] AS SELECT T1.column_1 FROM dbo.T1 (NOLOCK, FASTFIRSTROW) WHERE T1.column_1 = 1	Works	Works	Errors TSD4001: Invalid column name 'NOLOCK'. (SQL error = 207) TSD4001: Invalid column name 'FASTFIRSTROW'. (SQL error = 207) TSD4001: Parameters supplied for object 'dbo.T1' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. (SQL error = 215)
Using old join ANSI syntax, for example: CREATE PROCEDURE [dbo].[p_test] AS BEGIN SELECT T1.column_1 FROM dbo.T1, dbo.T2 WHERE T1.column_1 *= T2.column_1 RETURN 0; END	Works	Works	Error TSD4027: The query uses non-ANSI outer join operators ("=" or "="). To run this query without modification, please set the compatibility level for current database to 80 or lower, using stored procedure sp_dbcmptlevel. It is strongly recommended to rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER JOIN). In the future versions of SQL Server, non-ANSI join operators will not be supported even in backward-compatibility modes. (SQL error = 4147)

The above list examples are not exhaustive and do not represent the complete list of difference in database compatibility levels. Please see the SQL Server Books Online topic on sp_dbcmptlevel, it contains a list of differences. (Look for the label "Differences Between Lower Compatibility Levels and Level 90".)

Resolution:

So what do you need to do when you are running in to this problem? First you need to determine which version of Visual Studio Team System Database Edition you have and if you need to install the latest QFE or not.

Visual Studio 2005

If you are using the Visual Studio 2005 based version, you need to make sure that you install the latest QFE roll-up, which is documented in the following KB article:

KB 941278: Visual Studio 2005 Team System Database Professional Post Service Release 1 (SR1) Rollup Package #1

Visual Studio 2008

If you are using a Visual Studio 2008 RTM based version, you are OK and do not need to install an update; however if you are using a Visual Studio 2008 pre-release version (CTP, beta or RC) you do need to update to the RTM version, since the fix went in at the last moment.

Workaround

Now that you have identified which version you need, how do you work around the problem? We have added a way to set the database compatibility level inside the project, however there is no UI support to set this option. You need to follow the following steps.

Step 1: Unload the project

We will need to add a property to the project file, in order to do this you have to unload the project so that you can edit project file using the XML editor. Right click on the project node inside the Solution Explorer and choose "Unload Project".

Step 2: Add the CompatLevel property to the project file

The next step is to modify the project file to add the CompatLevel property.

Right click on the unloaded project in Solution Explorer and choose "Edit <project name.dbproj>".

This will open the project file inside the XML editor. You need to make sure you are adding the property to the right configuration block. By default there is only one configuration named 'Default'. Which is declared at the top of the project file, below you see the first 18 lines.

   1: <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">

   2:   <PropertyGroup>

   3:     <Configuration Condition=" '$(Configuration)' == '' ">Default</Configuration>

   4:     <Name>"DatabaseProject"</Name>

   5:     <SchemaVersion>2.0</SchemaVersion>

   6:     <ProjectGuid>{86c9eefc-ee75-4a7f-a518-b398f5922055}</ProjectGuid>

   7:     <ShowWizard>False</ShowWizard>

   8:     <OutputType>Database</OutputType>

   9:     <DBProduct>SQL Server 2005</DBProduct>

  10:     <RootPath>

  11:     </RootPath>

  12:     <ArithAbort>True</ArithAbort>

  13:     <NumericRoundAbort>False</NumericRoundAbort>

  14:     <AnsiNulls>True</AnsiNulls>

  15:     <ConcatNullYieldsNull>True</ConcatNullYieldsNull>

  16:     <AnsiPadding>True</AnsiPadding>

  17:     <AnsiWarnings>True</AnsiWarnings>

  18:     <QuotedIdentifier>True</QuotedIdentifier>

  19:     <...>

  20:   </PropertyGroup>

What you need to do is at the CompatLevel property by adding the following XML element: <CompatLevel>80</CompatLevel>. I suggest to place it under the DBProduct property, since this information is related.

   1: <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">

   2:   <PropertyGroup>

   3:     <Configuration Condition=" '$(Configuration)' == '' ">Default</Configuration>

   4:     <Name>"DatabaseProject"</Name>

   5:     <SchemaVersion>2.0</SchemaVersion>

   6:     <ProjectGuid>{86c9eefc-ee75-4a7f-a518-b398f5922055}</ProjectGuid>

   7:     <ShowWizard>False</ShowWizard>

   8:     <OutputType>Database</OutputType>

   9:     <DBProduct>SQL Server 2005</DBProduct>

  10:     <CompatLevel>80</CompatLevel>

  11:     <RootPath>

  12:     </RootPath>

  13:     <ArithAbort>True</ArithAbort>

  14:     <NumericRoundAbort>False</NumericRoundAbort>

  15:     <AnsiNulls>True</AnsiNulls>

  16:     <ConcatNullYieldsNull>True</ConcatNullYieldsNull>

  17:     <AnsiPadding>True</AnsiPadding>

  18:     <AnsiWarnings>True</AnsiWarnings>

  19:     <QuotedIdentifier>True</QuotedIdentifier>

  20:     <...>

  21:   </PropertyGroup>

Line 10 shows the required change.

Step 3: Reload the project

After you made the project change, adding the property to the project file, it is time to reload the project. Right click on the unloaded project node inside Solution Explorer and choose "Reload Project". This will reload the project.

NOTE: Make sure you have no errors when loading the project, because this will be an indication that your edits were not correct.

After you reload the project, the errors related to the database compatibility mode differences should have disappeared.

Restrictions

You can add the CompatLevel property to both SQL Server 2000 and SQL Server 2005 projects, however the values allowed for the database compatibility mode are restricted to: 80 and 90, other values are not supported.

Side effects

What are the side effects of adding and setting the value of the CompatLevel property?

The DesignDB instance will be set to the database compatibility level set in the project. When the property is not set explicitly the values are implicitly derived from the DBProject property value.
- <DBProduct>SQL Server 2000</DBProduct> implies database compatibility level 80
- <DBProduct>SQL Server 2005</DBProduct> implies database compatibility level 90

The database compatibility level will get propagated to the build script. For example when using a SQL Server 2005 project with the CompatLevel set to 80, a new build script you will contain:

   1:  CREATE DATABASE [$(DatabaseName)] ON ( NAME = N'PrimaryFileName', FILENAME = N'$(PrimaryFilePhysicalName)') LOG ON ( NAME = N'PrimaryLogFileName', FILENAME = N'$(PrimaryLogFilePhysicalName)') COLLATE SQL_Latin1_General_CP1_CS_AS

   2:  GO

3:

   4:  :on error resume

5:

   6:  EXEC sp_dbcmptlevel N'$(DatabaseName)', 80

   7:  GO

Where an incremental build will contain:
```
   1:  DECLARE @dbcompatlvl as int;
```
```
   2:  SELECT  @dbcompatlvl = cmptlevel
```
```
   3:  FROM    [master].[dbo].[sysdatabases]
```
```
   4:  WHERE   [name] = N'$(DatabaseName)';
```
```
   5:  IF (ISNULL(@dbcompatlvl, 0) != 80)
```
```
   6:  BEGIN
```
```
   7:      RAISERROR(N'The database compatibility level of the build script %i does not match the compatibility level of the target database %i. Verify whether your database project settings are correct and whether your build script is up to date.', 16, 127, 80, @dbcompatlvl) WITH NOWAIT;
```
```
   8:      RETURN;
```
```
   9:  END
```
```
  10:  GO
```

Summary

If you are relying on the SQL Server database compatibility level, to keep your code running, you need to set the CompatLevel property inside your project. If you want you can update your project templates to include the CompatLevel property so you do not forget to set it.

-GertD

Apply Test-Driven Development to your Database Projects

gertd — Sat, 16 Feb 2008 09:31:47 GMT

This months issue of MSDN Magazine features a great article about how to use and extend Database Unit Testing written by Jamie Laflen who is the developer and tech lead in my team responsible for Database Unit Testing, Data Generation, SQL Code Coverage and Build & Deploy. So this information comes straight from the source!

Check out: http://msdn.microsoft.com/msdnmag/issues/08/LA/DBUnitTesting/default.aspx

-GertD

Lorem ipsum

gertd — Wed, 13 Feb 2008 22:11:23 GMT

This morning I received email from the owner of the DbProGenerators project on CodePlex announcing the availability of the LoremTextGenerator, which is a data generator that creates Lorem ipsum texts. Please check out the CodePlex project site at http://www.codeplex.com/DbProGenerators for more details and to download the binaries and sources.

I am very pleased to see a community starting to evolve around our product, which is adding new abilities to the product by using the extension points provided. Feel free to send me email with any other extensions you have available for Visual Studio Team System Database Edition, or if you have requests, please send them as well, using the email link on this blog site.

Thanks,
-GertD

Self Referencing

gertd — Fri, 04 Jan 2008 09:42:17 GMT

Lately we have been getting questions about self-referencing database calls. What I mean with that is that you are referencing SQL objects using a 3-part name while referencing objects that reside inside your current database context.

For example:

   1: use Northwind

   2: go

3:

   4: SELECT * FROM Northwind.dbo.Categories

   5: go

Just to be clear, the use of self-referencing database calls does not add any value or functionality. In my opinion it only make the code more verbose and harder to maintain since you are dealing with literal references that you will need to update when you need to deploy to a different database name, which is why this technique was never promoted as a best never promoted as a best practice.

But based on the question we are receiving it seems that there are people that use this technique and want to use this in combination with DBPro.

Lets see want happens by creating a simple project that I will name NW which imports the Northwind database schema, after I have created the project I will add two objects, a stored procedure and a view which will both reference the NW database directly.

First we add the self referencing stored procedure, which looks like this:

   1: CREATE PROCEDURE [dbo].[selfref_proc]

   2: AS

   3: BEGIN

   4:     SET NOCOUNT ON

   5:     SELECT  [CategoryID],

   6:             [CategoryName],

   7:             [Description],

   8:             [Picture]

   9:     FROM    [NW].[dbo].[Categories]

10:

  11:     RETURN 0;

  12: END

NOTE: I am explicitly not using Northwind, but NW in this example.

The result of adding a self referencing stored procedure is that you will receive a TSD3025 warning

TSD3025: The following cross-database dependencies could not be verified: [NW].[dbo].[Categories], [NW].[dbo].[Categories].[CategoryID], [NW].[dbo].[Categories].[CategoryName], [NW].[dbo].[Categories].[Description], [NW].[dbo].[Categories].[Picture]. Your database application might fail at runtime when [dbo].[selfref_proc] is executed.

When you are adding a self referencing view, which looks like this:

   1: CREATE VIEW [dbo].[selfref_view]

   2: AS

   3:     SELECT  [CategoryID],

   4:             [CategoryName],

   5:             [Description],

   6:             [Picture]

   7:     FROM    [NW].[dbo].[Categories]

You will get an TSD4001 error and a TSD3024 warning.

TSD4001: Invalid object name 'NW.dbo.Categories'. (SQL error = 208)

TSD3024: The following cross-database dependencies of [dbo].[selfref_view] could not be verified: [NW].[dbo].[Categories], [NW].[dbo].[Categories].[CategoryID], [NW].[dbo].[Categories].[CategoryName], [NW].[dbo].[Categories].[Description], [NW].[dbo].[Categories].[Picture]. You might not be able to deploy the project. You can define a cross-database reference to resolve this warning.

The error is raised by the Design-time Validation database (DesignDB), since it use an arbitrary name for the scratch database which by definition is not NW.

So some of you might say, lets add Database Reference to your own DBMeta file, you are using a 3-part names and Database References are there to provide 3-part name resolution. This will not work, if you read the restrictions around database references closely, it states that:

Restrictions

Since we added this functionality in a service release, we have some restrictions, below you will find an overview of the most important ones with an explanation on why these restrictions exist in the current system.

Cyclic references: we do not support cyclic references. For example project A references project B and project B references A. We currently cannot support this because we cannot determine the correct build order in a guaranteed fashion (which project to build first) and since we always build the full database and cannot perform partial builds, cyclic references would result in to infinite builds.
Only 3 or 4-part names are resolved, dynamic queries using for example OpenQuery, OpenRowset or OpenDataSource can not be resolved because the shape of the output can only be determined by executing the actual query against the actual targeted data source. Database references do not solve all causes for warnings and errors cause by cross database references, only those caused by explicit 3 and 4-part name usage, not for any of the dynamic query executions strategies.
Self references are not allowed, in other words a database project cannot not establish a reference to its self. The underlying reason is that database reference contribute to a different namespace then the current project.
You can not use the same database reference to resolve 3 and 4-part names at the same time; a database reference either contributes objects to a 4-part or a 3-part namespace. In real life you can have a linked server pointing to a local database on the same instance, this means you can reference objects in that database in two ways: through a 3-part name: SELECT * FROM D.S.T and through a 4-part name: SELECT * FROM SVR.D.S.T. If you have this situation you either have to change all your code to use a single access path, or you need two references.
Variables used to identify 3 or 4-part name references need to be placed between square brackets or double quotes, to prevent parser errors.

The reason why you cannot resolve a self-reference through the current database reference implementation is that you would need to be able to build first, which and since then you would have to rebuild to resolve the references, invalidating the dbmeta file, so you would have to rebuild, and so on. In other words you would never finish building.

The conclusion therefore is that we currently cannot support self-referencing database call. The only option is to remove the self-referencing database part and use 2-part names instead.

-GertD

BTW: I am investigating if we can provide a workaround for this issue by adding a well-known variable like $(ThisDB) that could be used to abstract the current database context.

Is DesignDB In Use?

gertd — Wed, 19 Dec 2007 03:53:10 GMT

When Visual Studio Team System Database Edition opens a design-time validation database, it acquires an exclusive application lock on the DesignDB database using the following code.

   1:  EXEC @rc = sp_getapplock N'TSDATA', N'Exclusive', N'Session', 0, N'dbo';

A side effect of acquiring the application lock is that only a single Visual Studio instance can open the project using the same DesignDB instance, this is why the DesignDB name is stored in the <database project>.dbproj.user file which therefore should not be shared between. If you do share the <database project>.dbproj.user file and a second user will try to open the project it will get the following error dialog, indicating that the DesignDB instance associated with the project is already open.

You can use this knowledge to find out which DesignDB instances are actively being used by a Visual Studio instance by running the following query:

   1: SELECT  db_name([rsc_dbid]) AS [DesignDB]

   2: FROM    [master].[dbo].[syslockinfo]

   3: WHERE   [rsc_type] = 10

   4: AND     [req_ownertype] = 3

   5: AND     [req_refcnt] = 1

   6: AND     [rsc_text] like N'%[TSDATA]%'

If you have multiple instances of Visual Studio running and want to find out which process is holding an DesignDB instance open you can correlate it back to the process ID (PID) by using the following query:

   1: SELECT  DISTINCT [host_process_id] AS [PID]

   2: FROM    [master].[sys].[dm_exec_sessions] AS [es]

   3: JOIN    [master].[dbo].[syslockinfo] AS [li] ON [li].[req_spid] = [es].[session_id]

   4: WHERE   [li].[rsc_type] = 10

   5: AND     [li].[req_ownertype] = 3

   6: AND     [li].[req_refcnt] = 1

   7: AND     [li].[rsc_text] like N'%[TSDATA]%'

-GertD

Cleaning up DesignDB Leftovers

gertd — Wed, 19 Dec 2007 03:24:22 GMT

In the "DesignDB Location" blog post I described where the design-time validation database are created. The attentive reader would have wondered when design-time validation database file get cleaned up, since we create them at project creation time and attach or re-create at project open time. So when do they get removed?

The answer: DesignDB files don't get removed!

So the question is how do I clean-up the files left behind? The following stored procedure is an attempt to help you with this task. It identifies the files, checks if the files are not currently in use by an open database and when not you can delete the files, if you explicitly ask the procedure to do so.

Usage:

There are two use cases, the first is to identify files that are left behind, the second is to explicitly delete them.

Identifying leftovers:

The following three invocations have the same result:

EXEC [master].[dbo].[CleanupDesignDB]
EXEC [master].[dbo].[CleanupDesignDB] 0
EXEC [master].[dbo].[CleanupDesignDB] @ConfirmDeletionOfFiles = 0

It will generate the following type of output:

   1:  DefaultData directory: [C:\DBS\]

   2:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef.ldf]

   3:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef.mdf]

   4:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_0] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_00_633335867071557042.mdf]

   5:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_0] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_01_633335867071557042.ldf]

   6:  File in-use by database: [AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4] - [C:\DBS\AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4.ldf]

   7:  File in-use by database: [AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4] - [C:\DBS\AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4.mdf]

   8:  Will be deleting: [C:\DBS\NW_DB_ad914c71-d155-451b-9607-0d122c8a274c.ldf]

   9:  Will be deleting: [C:\DBS\NW_DB_ad914c71-d155-451b-9607-0d122c8a274c.mdf]

Line 1: Returns the directory that is being scanned based on the settings detected, in this example the C:\DBS directory on my notebook.

Lines 2-7: Identify DesignDB files which are detected but are currently in use by an open database. This implies you have one or more active Visual Studio instances open which have one or more database projects open.

NOTE: If you terminated Visual Studio prematurely because you killed the devenv.exe process or crashed you can also have open design-time validation databases.

The files identified in lines 2-7 can and will not be delete because they are in use.

Line: 8-9 Identify in this example two files that are not in use and match the naming pattern of the design-time validation database and therefore are candidates to be deleted.

Cleanup leftovers

After you identified the candidate files to delete, you can use the same procedure to actually delete them by setting the @ConfirmDeletionOfFiles parameter of the CleanupDesignDB procedure to 1. This way is your explicit acknowledgement that you want to delete the files identified.

The following two invocations will have the same result:

EXEC [master].[dbo].[CleanupDesignDB] 1
EXEC [master].[dbo].[CleanupDesignDB] @ConfirmDeletionOfFiles = 1

When you choose to delete the files the output of the procedure will reflect this as such:

   1:  DefaultData directory: [C:\DBS\]

   2:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef.ldf]

   3:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef.mdf]

   4:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_0] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_00_633335867071557042.mdf]

   5:  File in-use by database: [AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_0] - [C:\DBS\AWRef_DB_c3af5090-9bac-433f-bf9b-295d3d60b2ef_01_633335867071557042.ldf]

   6:  File in-use by database: [AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4] - [C:\DBS\AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4.ldf]

   7:  File in-use by database: [AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4] - [C:\DBS\AW_DB_389182d6-38c2-437b-bcd9-82ae8aa9b2e4.mdf]

   8:  Deleting: [C:\DBS\NW_DB_ad914c71-d155-451b-9607-0d122c8a274c.ldf]

   9:  Deleting: [C:\DBS\NW_DB_ad914c71-d155-451b-9607-0d122c8a274c.mdf]

As you can see lines 7-8 indicate the file is actually being deleted. When you run the procedure again the files will be gone!

The code:

This is the T-SQL code for the CleanDesignDB stored procedure.

   1:  -- ---------------------------------------------------------------------------------------

   2:  -- CleanupDesignDB.sql

   3:  -- Written by Gert E.R. Drapers (GertD@SQLDev.Net) - All Rights Reserved.

   4:  --

   5:  -- Disclaimer - Thoroughly test this script, execute at your own risk.

   6:  -- ---------------------------------------------------------------------------------------

   7:  USE master

   8:  GO

9:

  10:  IF (OBJECT_ID('[dbo].[CleanupDesignDB]') IS NOT NULL)

  11:      DROP PROC [dbo].[CleanupDesignDB]

  12:  GO

13:

  14:  CREATE PROC [dbo].[CleanupDesignDB]

  15:  @ConfirmDeletionOfFiles int = 0

  16:  AS

  17:  BEGIN

18:

  19:  SET NOCOUNT ON

20:

  21:  DECLARE @datadir nvarchar(260),

  22:          @rc      int

23:

  24:  -- We want explicit conformation if you want the proc to delete files

  25:  --

  26:  IF NOT (@ConfirmDeletionOfFiles = 0 OR @ConfirmDeletionOfFiles = 1)

  27:  BEGIN

  28:      RAISERROR(N'Incorrect value for parameter @ConfirmDeletionOfFiles possible values [0|1]', 1, 16, 1) WITH NOWAIT

  29:  END

30:

  31:  -- Check if xp_cmdshell usage has been enabled, by default this is turned off in SQL Server 2005

  32:  --

  33:  IF NOT EXISTS (

  34:      SELECT     *

  35:      FROM     [sys].[configurations]

  36:      WHERE    [name] = 'xp_cmdshell'

  37:      AND        [value_in_use] = 1)

  38:  BEGIN

  39:      RAISERROR(N'xp_cmdshell is not enabled, run exec sp_configure ''xp_cmdshell'', 1', 16, 1) WITH NOWAIT

  40:  END

41:

  42:  -- Get the DefaultData directory

  43:  --

  44:  EXEC @rc = [master].[dbo].[xp_instance_regread]

  45:          N'HKEY_LOCAL_MACHINE',

  46:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  47:          N'DefaultData',

  48:          @datadir output,

  49:          'no_output'

50:

  51:  -- Add slash to the end of the path if not present

  52:  --

  53:  IF ((@datadir IS NOT NULL) AND (CHARINDEX(N'\', @datadir, len(@datadir)) = 0))

  54:  BEGIN

  55:      SELECT @datadir = @datadir + N'\'

  56:  END

57:

  58:  -- Use same path as master if DefaultData path is not set (NULL)

  59:  --

  60:  IF (@datadir IS NULL)

  61:  BEGIN

  62:      SELECT    @datadir = SUBSTRING([physical_name], 0, CHARINDEX(N'master.mdf', [physical_name]))

  63:      FROM    [master].[sys].[database_files]

  64:      WHERE    [file_id] = 1

  65:  END

66:

  67:  PRINT 'DefaultData directory: [' + @datadir + ']'

68:

  69:  -- Temporary table to hold files inside directory

  70:  --

  71:  CREATE TABLE #f

  72:  (

  73:      [subdirectory]    nvarchar(260) not null,

  74:      [depth]         int not null,

  75:      [file]            int not null

  76:  )

77:

  78:  -- Insert all filenames in @datadir path in to temp table

  79:  --

  80:  INSERT INTO #f EXEC [master].[dbo].[xp_dirtree] @datadir, 1, 1

81:

  82:  -- Pattern match on distinct pattern of DesignDB naming, if no files found bail

  83:  --

  84:  IF NOT EXISTS (

  85:      SELECT    [subdirectory] AS [filename]

  86:      FROM    #f

  87:      WHERE     [file] = 1

  88:      AND       ([subdirectory] LIKE '%[_]DB[_]________[-]____[-]____[-]____[-]____________[.]_[dD][fF]'

  89:      OR        [subdirectory] LIKE '%[_]DB[_]________[-]____[-]____[-]____[-]____________[_]__[_]__________________[.]_[dD][fF]'

  90:             ))

  91:  BEGIN

  92:      PRINT N'No files found'

  93:      RETURN

  94:  END

95:

  96:  DECLARE filename_cursor CURSOR

  97:  READ_ONLY

  98:  FOR

  99:  SELECT    [subdirectory] AS [filename]

 100:  FROM    #f

 101:  WHERE     [file] = 1

 102:  AND       ([subdirectory] LIKE '%[_]DB[_]________[-]____[-]____[-]____[-]____________[.]_[dD][fF]'

 103:  OR        [subdirectory] LIKE '%[_]DB[_]________[-]____[-]____[-]____[-]____________[_]__[_]__________________[.]_[dD][fF]'

 104:         )

 105:

 106:  DECLARE @filename nvarchar(260),

 107:          @fullpath nvarchar(260),

 108:          @cmdstmt nvarchar(4000),

 109:          @fileexist int,

 110:          @db_id int

 111:

 112:  OPEN filename_cursor

 113:

 114:  FETCH NEXT FROM filename_cursor INTO @filename

 115:  WHILE (@@fetch_status <> -1)

 116:  BEGIN

 117:      IF (@@fetch_status <> -2)

 118:      BEGIN

 119:          SELECT @fullpath = @datadir + @filename

 120:

 121:          EXEC [master].[dbo].[xp_fileexist] @fullpath, @fileexist OUTPUT

 122:          IF (@fileexist = 1)

 123:          BEGIN

 124:              IF NOT EXISTS (

 125:                  SELECT  *

 126:                  FROM     [dbo].[sysaltfiles]

 127:                  WHERE     UPPER([filename]) = UPPER(@fullpath))

 128:              BEGIN

 129:                  IF (@ConfirmDeletionOfFiles = 0)

 130:                  BEGIN

 131:                      PRINT 'Will be deleting: [' + @fullpath +']'

 132:                  END

 133:                  IF (@ConfirmDeletionOfFiles = 1)

 134:                  BEGIN

 135:                      PRINT 'Deleting: [' + @fullpath +']'

 136:                      SELECT @cmdstmt = 'DEL "' + @fullpath +'"'

 137:                      EXEC [master].[dbo].[xp_cmdshell] @cmdstmt, no_output

 138:                  END

 139:              END

 140:              ELSE

 141:              BEGIN

 142:                  SELECT  @db_id = [dbid]

 143:                  FROM     [dbo].[sysaltfiles]

 144:                  WHERE     UPPER([filename]) = UPPER(@fullpath)

 145:

 146:                  PRINT 'File in-use by database: [' + db_name(@db_id) + '] - [' + @fullpath +']'

 147:              END

 148:          END

 149:          ELSE

 150:          BEGIN

 151:              PRINT 'File does not exist: [' + @fullpath +']'

 152:          END

 153:      END

 154:      FETCH NEXT FROM filename_cursor INTO @filename

 155:  END

 156:

 157:  CLOSE filename_cursor

 158:  DEALLOCATE filename_cursor

 159:

 160:  DROP TABLE #f

 161:

 162:  END

 163:  GO

Download: CleanDesign.sql

-GertD

DesignDB Location

gertd — Tue, 18 Dec 2007 22:48:24 GMT

As you might know Visual Studio Team System Database Edition uses a local SQL Server database instance to validate the correctness of the code inside the database project. When you create a project a local scratch database is create for validation purposes, when you close project the database gets detached and when you re-open the project it gets re-attached if the database file actually exist and did not change in between. If changes are detected, which is detected based on the file MD5, the database gets dropped and recreated.

In this blog post I want to discuss where the Design Validation Database, or DesignDB for short is being created.

When VSDB attaches or creates the DesignDB it first determines the location of the databases for the SQL Server instance you specified to be used in Tools->Options->Database Tools->Design-time Validation Database.

Where is DesignDB created?

VSDB determines the DesignDB location is through the following T-SQL query:

   1:  DECLARE @filepath        nvarchar(260),

   2:          @rc             int

3:

   4:  EXEC master.dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE',N'Software\Microsoft\MSSQLServer\MSSQLServer',N'DefaultData', @filepath output, 'no_output'

5:

   6:  IF ((@filepath IS NOT NULL) AND (CHARINDEX(N'\', @filepath, len(@filepath)) = 0))

   7:      SELECT @filepath = @filepath + N'\'

8:

   9:  IF (@filepath IS NULL)

  10:      SELECT    @filepath = [sdf].[physical_name]

  11:      FROM    [master].[sys].[database_files] AS [sdf]

  12:      WHERE    [file_id] = 1

13:

  14:  SELECT @filepath AS FilePath

First the code checks the SQL Server DefaultData setting in the Registry, since this setting is optional and by default not set when SQL Server gets installed, when this returns NULL the code gets the file path from the MASTER database.

NOTE: In the case we use the master data path the underlying code separates the file name from the file path, this is not done instead the query.

VSDB only uses the DefaultData location however you should also look at the DefaultLog location, so the following query is more generic:

   1:  DECLARE @datadir nvarchar(260),

   2:          @logdir  nvarchar(260),

   3:          @rc      int

4:

   5:  EXEC @rc = [master].[dbo].[xp_instance_regread]

   6:          N'HKEY_LOCAL_MACHINE',

   7:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

   8:          N'DefaultData',

   9:          @datadir output,

  10:          'no_output'

11:

12:

  13:  EXEC @rc = [master].[dbo].[xp_instance_regread]

  14:          N'HKEY_LOCAL_MACHINE',

  15:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  16:          N'DefaultLog',

  17:          @logdir output,

  18:          'no_output'

19:

  20:  SELECT  @datadir AS DefaultData,

  21:          @logdir AS DefaultLog

  22:  GO

Changing the location

What if you need or want to change the location where the design-time validation databases are created? You can achieve this by changing the DefaultData path Registry settings. You can do this in three ways.

Using SQL Server Management Studio
Using T-SQL script
Using the Registry Editor

NOTE: If you are changing the DefaultData location, you also want to change the DefaultLog location. VSDB will not use the DefaultLog setting, but when you issue a statement like CREATE DATABASE MyDB the MyDB.mdf file will end up in the DefaultData location while the MyDB_log.LDF file will end up in the DefaultLog location.

Using SSMS

You can change the DefaultData path using SSMS (SQL Server Management Studio) via the Server properties. After you started SSMS, right click on the server name and choose Properties, this will launch the Server Properties dialog.

At the bottom of the dialog under the "Database default locations" line you will find two text boxes, labeled Data and Log. The Data one reflects the state of the DefaultData and Log the DefaultLog Registry value. You can change these values in the dialog and hit OK, or you can choose the Script option and you will get the T-SQL script to apply the change using the EXEC xp_instance_regwrite statement. Using SSMS has the advantage you can browse the server side directory structure which reduces the change you enter a directory value that does not exist.

NOTE: The directory value provided does not get validated, neither by the SSMS UI or by SQL Server when changed!

Using T-SQL

You do not have to use SSMS to make these changes, you can simply execute the following query to set the location of the DefaultData and DefaultLog directory.

Set location using T-SQL:

   1:  DECLARE @datadir nvarchar(260),

   2:          @logdir nvarchar(260),

   3:          @rc int

4:

   5:  SELECT  @datadir = N'c:\temp',

   6:          @logdir = N'c:\temp'

7:

   8:  EXEC @rc = [master].[dbo].[xp_instance_regwrite]

   9:          N'HKEY_LOCAL_MACHINE',

  10:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  11:          N'DefaultData',

  12:          N'REG_SZ',

  13:          @datadir

14:

  15:  EXEC @rc = [master].[dbo].[xp_instance_regwrite]

  16:          N'HKEY_LOCAL_MACHINE',

  17:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  18:          N'DefaultLog',

  19:          N'REG_SZ',

  20:          @logdir

21:

  22:  EXEC @rc = [master].[dbo].[xp_instance_regread]

  23:          N'HKEY_LOCAL_MACHINE',

  24:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  25:          N'DefaultData',

  26:          @datadir output,

  27:          'no_output'

28:

29:

  30:  EXEC @rc = [master].[dbo].[xp_instance_regread]

  31:          N'HKEY_LOCAL_MACHINE',

  32:          N'Software\Microsoft\MSSQLServer\MSSQLServer',

  33:          N'DefaultLog',

  34:          @logdir output,

  35:          'no_output'

36:

  37:  SELECT  @datadir AS DefaultData,

  38:          @logdir AS DefaultLog

  39:  GO

Using the Registry Editor

When using the Registry Editor you first have to find the correct hive location in the Registry for the SQL Server instance, which is easy to get wrong since the difference between instances is abstracted through a ID. The previous two methods abstract you from having to do this.

You first have to look up the instances in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL

Which points you to an hive location in this example MSSQL.1
REG_SZ: SQL90 = MSSQL.1

Then you can use this information to locate the hive for instance name SQL90

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer
REG_SZ: DefaultData = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA
REG_SZ: DefaultLog = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA

Important: RESTART REQUIRED!

No matter which technique you used to change the values for DefaultData or DefaultLog, you always need to restart the SQL Server service in order for the new values to take effect!

After you have restart SQL Server you should restart VSDB and your DesignDB databases will now reside in the newly defined location.

-GertD

Visual Studio Team System 2008 Database Edition

gertd — Thu, 22 Nov 2007 02:26:14 GMT

Now that Visual Studio 2008 is available, the question arises what has changed for Visual Studio Team Edition for Database Professionals in the 2008 edition?

Not much is the answer. Since our first release was done completely out-of-band while other teams were actively working on the Visual Studio 2008 release, our main goal was to integrate in to main Visual Studio 2008 (aka. Orcas) code base. However we did make some changes that you should be aware of.

What changed:

First of all we have a new name, the official new name is "Visual Studio Team System 2008 Database Edition". This creates a new dilemma, what is the shortest way to indicate our product, because VSDE refers to the Visual Studio Team System Developer Edition. VSDB seems an appropriate alternative to use.
No more additional setup. In Visual Studio Team System 2008, we are completely integrated in the standard setup, so no more additional downloads. All you have to do is to make sure the Team Database Edition option is checked.
The Visual Studio Team System 2008 Database Edition is based on the v1.0 functionality plus the Service Release 1 functionality; this means that database references, file groups and SQLCMD variables support is part of the standard product.
We fixed 71 defects.

Eight of the issues were reported through Microsoft Connect:

Besides that we fixed 13 other user reported defects. The remainder were internally found issues.
One of the main defects addressed in this release has to do with automatically updating the underlying schema model when changes are made to the underlying source code representation, outside the direct control of the project system. A common example is when you are performing a sync operation from source code control. I discussed the issue in an earlier blog name "External Changes".
This change adds a check box to the Tools->Options->Database Tools->Design-time Validation Database options page. By default the option will be checked indicating you want to automatically update the schema model when changes occur.

Solution Explorer performance improvements, the Visual Studio Core team has been making some great improvements that will improve your overall performance, especially when your project has large number of objects stored under a single node instead Solution Explorer.

What did not change:

The database project functionality is only available in two of the Visual Studio Team System SKU's

Visual Studio Team System 2008 Database Edition
Visual Studio Team System 2008 Team Suite (including the trial edition)

The functionality that was made available through Power Tools for 2005, remains inside the Power Tools for the 2008 release, we are trying to release a new Power Tools release targeting 2008 later this month.

What is next?

Now that we are done with Visual Studio 2008, we are all working on our next big deliverable which is Visual Studio Team System Code Name "Rosario".

Thanks,
-GertD

Home of the Data Dude : VSDBPro

More Team Developer + Data Edition Merge Information

Team Developer + Team Data = Team Developer!

Trace Helper

Event Monitor

Enabling the Event Monitor

Visual Studio Team Edition for Database Professionals (2005)

Visual Studio Team System 2008 Database Edition

Visual Studio Team System 2008 Database Edition GDR

Launching the Event Monitor

Using the Event Monitor

Tech&#183;Ed 2008 Developers

Session list:

Sessions details:

DVP310 Agile Database Development (level 300)

TLA310 End-to-End Database Development Using Microsoft Visual Studio Team System 2008 Database Edition (level 300)

DAT326 Supporting Microsoft SQL Server 2008 within Microsoft Visual Studio Team System Database Edition (level 300)

DAT01-TLC Managing Database References in Microsoft Visual Studio Team System 2008 Database Edition (level 400)

TEO Panel _25 Testing the SQL Database (panel discussion)

DAT02-TLC Microsoft Visual Studio Team System 2008 Database Edition: Integrating Database Developers in Your Software Management Life Cycle (level 200)

TLA320 The Microsoft Visual Studio Team System Database Project Ecosystem: Integrating ALM and Database Tools via Extensibility (level 300)

DAT03-TLC Customization of Data Generation Using Microsoft Visual Studio Team System 2008 Database Edition (level 400)

MSDB Reference Projects

VSDB 2005 Service Release 1 Roll-up Package 1 (KB941278)

Database Compatibility Level

Resolution:

Visual Studio 2005

Visual Studio 2008

Workaround

Step 1: Unload the project

Step 2: Add the CompatLevel property to the project file

Step 3: Reload the project

Restrictions

Side effects

Summary

Apply Test-Driven Development to your Database Projects

Lorem ipsum

Self Referencing

Restrictions

Is DesignDB In Use?

Cleaning up DesignDB Leftovers

Usage:

Identifying leftovers:

Cleanup leftovers

The code:

DesignDB Location

Where is DesignDB created?

Changing the location

Using SSMS

Using T-SQL

Using the Registry Editor

Important: RESTART REQUIRED!

Visual Studio Team System 2008 Database Edition

What changed:

What did not change:

What is next?

Tech·Ed 2008 Developers