Home of the Data Dude : VS2008

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

Channel 9 VSDB 2008 GDR Interview

gertd — Tue, 03 Jun 2008 19:09:28 GMT

We just released a new Channel 9 interview that covers the Visual Studio Team System 2008 Database Edition GDR functionality that we introduced today.

http://channel9.msdn.com/posts/briankel/New-GDR-Announced-for-Visual-Studio-Team-System-2008-Database-Edition/

-GertD

VSTS 2008 Database Edition GDR June CTP

gertd — Tue, 03 Jun 2008 19:05:28 GMT

Today, at Tech*Ed 2008 Developer, we announced the immediate availability of the first public CTP of the Visual Studio Team System 2008 Database Edition GDR.

GDR stands for General Distribution Release. The GDR will be an out-of-band release enabling support for SQL Server 2008. It also introduces the new product architecture, which for those of you who are keeping up with the code names, is work that is a direct result of the "Rosario" project.

What is in the GDR?

In addition to enabling SQL Server 2008 database projects, the GDR release incorporates many of the previously released Power Tools functionality as well as several new features. The new features include explicit separation of Build and Deploy, separation of Database and Server project, improved project reference support, T-SQL Static Code Analysis and integration with SQL-CLR projects.

Architectural changes

No more DesignDB; one of the most important architectural changes is that the Database Edition no longer requires a local SQL Server instance to host the "Design Database" to open and validate a database project.
Single model, everything is now loaded in a single model representation. The model now represents all object types, which removes the need to have certain objects represented as Pre or Post Deployment scripts. This means that for example logins, rules, defaults, asymmetric keys, symmetric keys, certificates, etc. are now schema objects and therefore fully participate in schema comparison and build/deploy. Pre or Post Deployment scripts still exist, but are only used to perform none schema object related operations.
The model is no longer 100% memory resident, in today's version all model information has to reside in memory, this change dramatically lowers the memory consumption of the product.
Provider based, the underlying implementation of the project system and schema model are changed to be provider based. Providers are refer to as "Database Schema Providers" or DSP's for short. The GDR release will ship with 3 providers supporting SQL Server: 2000, 2005 and 2008. However if you watch the Tech*Ed keynote this morning, you saw that IBM is working on a provider to support DB2 and there are others that are working on providers for other database management systems.
- Providers are not restricted to relational database systems, in the future we will be adding providers that support dimensional and hierarchal data stores.

Project System

Database & Server project separation
- We separated out the existing database project in to two project flavors: database and server. The server project represent those schema objects that are server wide, for example logins, linked servers, server side DDL triggers etc. Database projects represent the objects inside the user database. The split enables a team to define a standard a configuration for their SQL servers and reference it from their Database Projects. The goals is to have a single point of definition and to be able to share this definition between projects and deployments.
  - The separation is implemented using a property inside the project file. There are effectively 3 modes: server, database and hybrid. The hybrid project represents the overloaded project model as it exists today where server and database objects are mixed inside a single project. This model is there to support existing project upgrades.
Partial projects
- Allow code sharing between projects by including files from a different project, where the code is included "as-is" from the originating project and the source code control ownership remains with the originating project. This enables code reuse between projects and while resulting in a single deployment unit.
Composite projects
- Composite projects, enables database projects and/or .dbschema files to contribute to another project. This enables the separation of development roles and responsibilities and composition of Databases using multiple projects. It extends the existing database reference implementation, by allowing to contribute in to the same database, where the existing database projects have to represent 3 or 4 part name references.
Single sourcing of external artifacts
- You can now create a reference to a SQL-CLR (VB.NET or C#) project, or the binary output of a project and turn it in to a ASSEMBLY inside the project. This enables single sourcing of artifacts that are developed outside the context of the database project. For the final release we will also allow references to XSD files which will become XML Schema Collections inside the database schema.

SQL Server 2008 Support

The GDR adds a new project for supporting SQL Server 2008. The June CTP has support of the new SQL Server 2008 data types, both intrinsic (date, datetime2, datetimeoffset, time), build-in SQL-CLR types (geography, geometry, hierarchyid), support for the new DML MERGE syntax and support for table typed parameters. The remaining SQL Server 2008 syntax and functionality will be added in future CTP's.

Build & Deploy

One of the other main changes in the GDR is the separation of the build and deployment process. Build now produces a single portable artifact file, a .DBSCHEMA file. The DBSCHEMA file is an XML representation of your complete schema. The DBSCHEMA is then fed in to the redistributable deployment engine.
The deployment engine now uses the exact same database model as Schema Compare, which guarantees the same results between the two parts of the system.

Refactoring

The biggest change in refactoring is the addition of a patented implementation of a feature named "Preservation of Intent". This enables the deployment of refactoring changes as intended by the user. For users this means that renames are deployed as renames not as drop/add statements, move aschemas as move schemas etc.
Besides that we are adding new refactoring types that we previously in the Power Tools:
- Wildcard Expansion
- Move Schema
- Fully Qualify
And we are enabling extensibility for refactoring which enables users to develop and deploy custom refactoring types and targets.
- Types are the refactoring operations, where targets are the artifacts you want to apply the refactoring operation to. An example of a refactoring type is: table split or upper case all keywords. An example of a refactoring target is an Reporting Services RDL file, which contains references to database schema objects, which if you change thos, you want to update them as part of the refactoring operation.

Schema Compare

Schema Compare now uses the same underlying database model as build and deploy, guaranteeing fidelity between the results. This allows the user to compare any combination of Database Projects (.dbprj), live Databases or .DBSCHEMA files. So comparing project to project, project with a DBSCHEMA file, or a DBSCHEMA file with a live database.
We added the ability to limited the schema comparison based on object types (Object Type Filtering) and we added additional Ignore filtering options.
We also enabled the substitution of SQLCMD variables, allowing correct comparison when using SQLCMD variables for references or in other parts of your code.

T-SQL Static Code Analysis

T-SQL Static Code Analysis, and the accompanying MSBuild task, are now part of the main product.
And we added the ability to develop and deploy your own custom T-SQL Static Code Analysis rules.

Dependency Viewer

The Power Tools to view the dependency relationship between objects inside your schema, is now part of the base product.

Database Unit Testing

Database unit testing now supports execution of tests using different ADO.NET providers and it also enables unit testing when using multiple database projects.

• Data Generation

We made some general design-time enhancements Data Generation like adding support for undo/redo and separation of the population status into new display window.
The Foreign key generator can now be replaced by custom generator.
And we made some runtime enhancements, by default the Data Generator now uses the SqlBulkCopy interface to populate target tables, which results in a general performance improvement during data load time.
We also introduced the concept of Data Sinks which allow the user to register different outputs, for example we can generate data to files instead of to a live database, so data can be loaded out-of-band using BCP or BULK INSERT.
And last but not least we were able to significantly trim the size of the .DGEN file.

Public extensibility:

The last piece we changed in the GDR is to expose more extensibility points in to the system. In the GDR we are not allowing new providers to be plugged in this will be available in the next release, but we do allow users to extend the system by writing their own:

Data Generators
(Statistical) Data Distributions
Test Conditions
T-SQL Static Code Analysis Rules
Refactoring Types
Refactoring Target

We also made the deployment engine a redistributable component, so you can deploy DBSCHEMA files programmatically.

So where to get the GDR?

All of this is part of the Visual Studio Team System 2008 Database Edition GDR June CTP which is available right now! Please see the download page.

Make sure you have the prerequisites installed, which means installing Visual Studio 2008 SP1 beta.

Feedback, questions, bugs, suggestions

Please post questions to the MSDN Visual Studio Team System - Database Professionals forum. For bugs, ideas and suggestions please use the Microsoft Connect site https://connect.microsoft.com/VisualStudio and fill them using the Visual Studio Team System 2008 Database Edition GDR link.

Thanks,
-GertD
Group Engineering Manager
Visual Studio Team System Database Edition

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

Command line SQL Static Code Analysis

gertd — Tue, 19 Feb 2008 01:06:05 GMT

We have had a lot of requests from users asking us to make T-SQL Static Code Analysis available at build time and from the command line. The latest Visual Studio Team System 2008 Database Edition Power Tool release, adds this ability to the product through a new MSBuild task. In this blog post I will go through the step that you need to follow to enable and use T-SQL Static Code Analysis from the command line.

Step 0: Install the Power Tools

You first need to install the latest Power Tools for Visual Studio Team System 2008 Database Edition.

Step 1: Create a new database project or open an existing one

We need a database project, either use an existing one, or simple create a test project, from example using the pubs database. That is what I will use for this example.

Step 2: Unload the project

We will need to add a entry to the project file to import the MSBuild .targets file for Power Tools. 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 3: Import the Microsoft.VisualStudio.TeamSystem.Data.PowerTools.Tasks.targets file

The next step is to modify the project file to add an import statement to include the Microsoft.VisualStudio.TeamSystem.Data.PowerTools.Tasks.targets file which contains the MSBuild task for T-SQL Static Code Analysis. Right click on the unloaded project in Solution Explorer and choose "Edit <project name.dbproj>".

This will open the .dbproj file inside the Visual Studio XML editor. Now we need to add an import statement to load the .target file. If you search for "<Import" inside the project file you will find the regular import which loads the normal MSBuild tasks for the database project like the SqlBuildTask and the SqlDeployTask.

   1: <!--Import the settings-->

   2: <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\TeamData\Microsoft.VisualStudio.TeamSystem.Data.Tasks.targets" />

We need to add a reference to the Power Tools targets file.

   1: <!--Import the settings-->

   2: <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\TeamData\Microsoft.VisualStudio.TeamSystem.Data.Tasks.targets" />

   3: <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\TeamData\Microsoft.VisualStudio.TeamSystem.Data.PowerTools.Tasks.targets" />

Step 4: Reload the project

After you made the project change, including the new targets 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.

Step 5: Start a "Visual Studio 2008 Command Prompt"

The next step is to run T-SQL Static Code Analysis from the command line, in order to do so we need a command prompt that has the PATH set correctly so we can call MSBuild.exe. Visual Studio creates a shortcut in the menu structure that will launch a command prompt with the correct settings.

When you started the command prompt navigate to the directory where you project file is located that you changed in the previous step.

Step 6: Run T-SQL Static Code Analysis from the command-line

From the command prompt run: msbuild pubs.dbproj /t:SqlAnalysis

NOTE: The results file is created in the output directory, which by default is the SQL directory

Step 7: Look at the results

When executing the project using the SqlAnalysis target, an XML file is created that contains the results, named StaticCodeAnalysis.Results.xml. This file contains the information that is normally displayed in the Visual Studio "Error List".

When you open the file in VS it will look like this:

   1: <?xml version="1.0" encoding="utf-16" standalone="no"?>

   2: <Problems>

   3:   <Problem>

   4:     <Rule>Microsoft.Design#SR0010</Rule>

   5:     <ProblemDescription>You should avoid using the following join syntaxes, which have been deprecated: Table1.Id = Table2.Id, Table1.Id *= Table2.Id, Table1.Id =* Table2.Id. You should use the newer syntax, which uses the JOIN keyword.</ProblemDescription>

   6:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.reptq2.proc.sql</SourceFile>

   7:     <Line>4</Line>

   8:     <Column>14</Column>

   9:     <Severity>Warning</Severity>

  10:   </Problem>

  11:   <Problem>

  12:     <Rule>Microsoft.Design#SR0010</Rule>

  13:     <ProblemDescription>You should avoid using the following join syntaxes, which have been deprecated: Table1.Id = Table2.Id, Table1.Id *= Table2.Id, Table1.Id =* Table2.Id. You should use the newer syntax, which uses the JOIN keyword.</ProblemDescription>

  14:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.reptq2.proc.sql</SourceFile>

  15:     <Line>4</Line>

  16:     <Column>23</Column>

  17:     <Severity>Warning</Severity>

  18:   </Problem>

  19:   <Problem>

  20:     <Rule>Microsoft.Design#SR0010</Rule>

  21:     <ProblemDescription>You should avoid using the following join syntaxes, which have been deprecated: Table1.Id = Table2.Id, Table1.Id *= Table2.Id, Table1.Id =* Table2.Id. You should use the newer syntax, which uses the JOIN keyword.</ProblemDescription>

  22:     <SourceFile>c:\work\pubs\Schema Objects\Views\dbo.titleview.view.sql</SourceFile>

  23:     <Line>4</Line>

  24:     <Column>15</Column>

  25:     <Severity>Warning</Severity>

  26:   </Problem>

  27:   <Problem>

  28:     <Rule>Microsoft.Design#SR0010</Rule>

  29:     <ProblemDescription>You should avoid using the following join syntaxes, which have been deprecated: Table1.Id = Table2.Id, Table1.Id *= Table2.Id, Table1.Id =* Table2.Id. You should use the newer syntax, which uses the JOIN keyword.</ProblemDescription>

  30:     <SourceFile>c:\work\pubs\Schema Objects\Views\dbo.titleview.view.sql</SourceFile>

  31:     <Line>4</Line>

  32:     <Column>23</Column>

  33:     <Severity>Warning</Severity>

  34:   </Problem>

  35:   <Problem>

  36:     <Rule>Microsoft.Performance#SR0005</Rule>

  37:     <ProblemDescription>You might cause a table scan when you use an expression that starts with "%" in the LIKE predicate. </ProblemDescription>

  38:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.reptq3.proc.sql</SourceFile>

  39:     <Line>6</Line>

  40:     <Column>73</Column>

  41:     <Severity>Warning</Severity>

  42:   </Problem>

  43:   <Problem>

  44:     <Rule>Microsoft.Performance#SR0007</Rule>

  45:     <ProblemDescription>You have specified a nullable column that is not wrapped with the ISNULL function. This practice can cause the final result to be evaluted as NULL for the predicate.</ProblemDescription>

  46:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.byroyalty.proc.sql</SourceFile>

  47:     <Line>4</Line>

  48:     <Column>7</Column>

  49:     <Severity>Warning</Severity>

  50:   </Problem>

  51:   <Problem>

  52:     <Rule>Microsoft.Performance#SR0007</Rule>

  53:     <ProblemDescription>You have specified a nullable column that is not wrapped with the ISNULL function. This practice can cause the final result to be evaluted as NULL for the predicate.</ProblemDescription>

  54:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.reptq3.proc.sql</SourceFile>

  55:     <Line>6</Line>

  56:     <Column>7</Column>

  57:     <Severity>Warning</Severity>

  58:   </Problem>

  59:   <Problem>

  60:     <Rule>Microsoft.Performance#SR0007</Rule>

  61:     <ProblemDescription>You have specified a nullable column that is not wrapped with the ISNULL function. This practice can cause the final result to be evaluted as NULL for the predicate.</ProblemDescription>

  62:     <SourceFile>c:\work\pubs\Schema Objects\Stored Procedures\dbo.reptq3.proc.sql</SourceFile>

  63:     <Line>6</Line>

  64:     <Column>27</Column>

  65:     <Severity>Warning</Severity>

  66:   </Problem>

  67: </Problems>

Step 8: Clean up the results

If you want to clean up the resulting file produced by the static code analysis run, simply run:

msbuild pubs.dbproj /t:ScaClean

This will remove the results file.

Conclusion:

Following the steps outlined before enable you to run T-SQL Static Code Analysis from the command line, you can use the same step to integrate this in to your Team Build environment, but you have to make sure that you install the Power Tools on the build server before you can use this.

-GertD
"DataDude" Group Engineering Manager

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

File Bound Generator

gertd — Sun, 17 Feb 2008 06:31:14 GMT

An other new addition to the Visual Studio Team System 2008 Database Edition - Power Tools release is the File Bound Generator. This data generator grovels through files inside a directory or optionally through its subdirectories, based on some search filter you provide and loads the content of the file in to a column value. The file content is either represented as text or as binary data. The generator is shared-instancing enabled, which means that the same file can be bound to multiple columns inside the same row while having to load it only once.

Let walk through an example which leverages the file bound generator to load data in to a table.

Step 0: Install the Power Tools

You first need to install the latest Power Tools for Visual Studio Team System 2008 Database Edition.

Step 1: Create a new project and add a table

The first step is to create a new database project, in this example I am using a SQL Server 2005 project named "testdb", since I want to leverage the NVARCHAR(MAX) and VARBINARY(MAX) data types, otherwise use NTEXT and IMAGE instead.

After having created the project add a new table which we will name [dbo].[files] with the following shape:

   1: CREATE TABLE [dbo].[files]

   2: (

   3:     [file_id]    int identity not null,

   4:     [file_name]  nvarchar(256) not null,

   5:     [file_text]  nvarchar(max) null,

   6:     [file_bin]   varbinary(max) null,

   7: );

After you created the project and the table, make sure that you build and deploy project.

Step 2: Create a new Data Generation Plan

Next add a new Data Generation Plan, by right clicking on the Data Generation Plan folder in Solution Explorer and choose: "Add... New Item... Data Generation Plan"

This will add a new Data Generation Plan to your project and automatically bind the columns of the tables inside your project to the default data generator.

Step 3: Create some test input

In order to create some test files we can load and also demonstrate how shared-instancing works I am using the following batch file:

   1: @rem CreateFiles.cmd

   2: @echo off

3:

   4: for /L %%I in (1, 1, 1000) do call :CREATE %%I

   5: goto END

6:

   7: :CREATE

   8: @echo filename%1.txt > filename%1.txt

9:

  10: :END

Create a folder, for example C:\TEST, create or copy the CreateFiles.cmd file in to the directory you just created and run the batch file. This will create a 1000 files with sequential names and the content of the file being the file name so we can use it for correlation purposes.

Step 4: Configure the File Bound Generator

The default configuration of the plan will look like this:

The next step is to assign file bound generator to the file_name, file_text and file_bin columns.

After you assigned the generator you need to set the Generator Output, by default the generator binds to the coercion type, so the file_name and file_text will bind to String Result since they are NVARCHAR columns, the file_bin column will by default bind to the Binary Result since its type is of VARBINARY.

We want the file_name column to bind to the name of the file we are importing, which means you need to change the Generator Output to File Name, the other columns are bound to the output that we need.

Bind the generator output to the columns, bind file_name to File Name, file_text to String Result and file_bin to Binary Result

The end result should look like this:

Next step is to configure generators for the 3 columns that we assigned to the file bound generator. If you want shared-instancing to work you need to make sure that the generator configuration of all 3 columns assigned to the file bound generator is identical.

Configuring the columns:

Step 5: Execute the Data Generation Plan

Now that we have configured the generators for all columns in the files table, we can generate some data, by executing the Data Generation Plan. Before we do this change the numbers of rows to be generated for the files table from 50 to 1000, to match the number of files we generated. Then hit F5, to execute the plan.

Step 6: Display the results

Once the executing is finished, open up the T-SQL editor and execute the following query.

   1: SELECT   *

   2: FROM     [dbo].[files]

   3: ORDER    BY [file_id]

The results:

If you click on the first binary entry for file_id = 1 you will find that the filename in the binary content matches the file_name and file_text.

Conclusion

The File Bound Generator allows you to load the content of files in to your database and the shared-instancing functionality makes sure that you can pull the absolute file path in to an other column in the same row when generating test data.

-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

Data Generation Wizard

gertd — Fri, 15 Feb 2008 10:34:06 GMT

One of the new features in the Visual Studio Team System 2008 Database Edition - Power Tools release is the addition of the Data Generation Wizard. The Data Generation Wizard is an item template wizard that allows you to create and configure a data generation plan by pointing it at an existing database, which has the same schema as the underlying database project, and configure each column inside each table with a sequential data bound generator. When finished you have a configured data generation plan that pulls all rows from the existing database in to your target database.

Lets step through the process.

Step 1: Add a new Data Generation plan using the Data Generation Wizard.

Inside an existing database project, select Add... New Item... and select the "Data Generation Wizard" option. In this example I am using the good old trusted pubs database as my sample database.

Step 2: Launch the Data Generation Wizard

Once you selected the Data Generation Wizard, you will get the main page of the wizard. Above you see the default state of the wizard.

Step 3: Select your source database

The next step is to select the database that you want to pull the data from, in this example I am pulling from the pubs sample database. If you have not configured a connection to the specific target database, you can create one using the New Connection... option or you can change existing connection definitions using the Edit Connection... option.

Once you select the database there are a couple of options you can select or set, lets walk through these:

Set the number of rows to generate...
This option will configure the "Rows to Insert" value of data generation plan, to exactly the number of rows that are inside the source database.
Replace the foreign key generator with values form the target database...
If you check this option the wizard will pull the foreign key values from the source database, instead of leveraging the foreign key data generator
Number of failed rows...
This option configures the error threshold for the number of failures to be allowed before terminating the population of a table
Number of failed tables...
This option configures the error threshold for the number of failures to be allowed before the terminating execution of the data generation plan

Step 4: Run the wizard

When you hit OK, you will see a Status window which will display the progress information of the creation and configuration of the data generation plan.

Below you see the status information from creating the data generation plan for the pubs database.

Retrieving data from pubs.
Data retrieval complete.
Starting merge of data generation plan with database schema.
Completed.
Resetting all target row counts to match target database
Setting table [dbo].[authors] to 23 rows
Setting table [dbo].[discounts] to 3 rows
Setting table [dbo].[employee] to 43 rows
Setting table [dbo].[jobs] to 14 rows
Setting table [dbo].[pub_info] to 8 rows
Setting table [dbo].[publishers] to 8 rows
Setting table [dbo].[roysched] to 86 rows
Setting table [dbo].[sales] to 21 rows
Setting table [dbo].[stores] to 6 rows
Setting table [dbo].[titleauthor] to 25 rows
Setting table [dbo].[titles] to 18 rows
Populating columns with Sequential databound generator
Configuring table dbo.authors to be databound
Configuring table dbo.discounts to be databound
Configuring table dbo.employee to be databound
Configuring table dbo.jobs to be databound
Configuring table dbo.pub_info to be databound
Configuring table dbo.publishers to be databound
Configuring table dbo.roysched to be databound
Configuring table dbo.sales to be databound
Configuring table dbo.stores to be databound
Configuring table dbo.titleauthor to be databound
Configuring table dbo.titles to be databound
Saving to file 'c:\work\pubs\Data Generation Plans\DataTransformPlan1.dgen'
Completed

As you can conclude from the status output the wizard configures the data generation plan in two phases. First it configures the row counts and secondly in configures the generators for each column inside each table. If you did not select the option to propagate row counts the first phase will be skipped.

Step 5: The resulting data generation plan

Now that the wizard is finished, lets look at the results. First we will look at the data generation plan. We will see that the row counts are configured for each respective table.

Step 6: The resulting column configuration

If we look at the column configurations we see that in our example the foreign keys are generated using the foreign key generator and the other values are pulled from the database. Note that we are using the sequential databound generator, which support multi-instancing. This means that columns values are matched per row, the regular databound generator does not have this ability to correlate column values within a single row!

Step 7: Running the generation plan

Now that we have a data generation plan, lets runs it. We created a clean database from our project named pubs2 and we are going to generate straight in to this.

If you are using the real pubs database you will find that this will fail. For a good reason, because the employee_insupd trigger inside the schema that will cause a rollback if the job id does not have a certain value. If you are using the default setting, the plan for the employee table will look like this:

The job id foreign key generator is not configured correctly to satisfy the employee_insupd trigger.

If you selected the option "Replace the foreign key generator with values form the target database..." you plan for the employee table looks like this:

Note that the job_id column is also pulled from the database, so when you used that option you will satisfy the trigger and the plan will just work!

Step 8: Showing the results

Now that we executed the plan, lets check the results, by opening up the T-SQL Editor and fire off a simple query "SELECT * FROM sales" to see if the content made it over.

Conclusion:

The Data Generation Wizard allows you to quickly configure a data generation plan that pulls all rows from an existing SQL Server database. The wizard will only allow you to pull information from an SQL Server database, because the schema of the objects inside the database has to match the table inside the database project.

We hope this new feature saves you time!

-GertD
"DataDude" Group Engineering Manager

Visual Studio Team System 2008 Database Edition Power Tools

gertd — Fri, 15 Feb 2008 08:59:06 GMT

The “DataDude” team is happy to announce the availability of the Power Tools for Visual Studio Team System 2008 Database Edition.

The Power Tools for 2008 contains all the functionality we shipped in 2005 plus:

Command line SQL Static Code Analysis execution through MSBuild, this was the biggest customer request, which is why I was holding the release. This enables SQL Static Code Analysis to be an integrated part of Team Build!
Data Generation Wizard; this is another customer request where we allow users to create a new data generation plan by pointing at an existing database, the plan will be fully configured by the wizard to pull all data from the database using the Sequential Databound Generator. This way users can use an existing data set and only override columns which impose risks because of for example privacy concerns and save about half a day or more of configuring a data generation plan from scratch, one column at the time.
File based data generator; this allows you to insert the content of files in to the database (works for string and binary, not for XML yet).
XML based data generator; this allows you to generate XML based on an XSD (the XSD has to be provided as file right now, and cannot be selected from database or inherited from the data type).
Unique Regular Expression generator; this adds the ability to generator unique values using the RegEx String generator.
Refactoring Command Generator has been made available as a MSBuild task for better project build integration so it can be made part of the pre-build and pre-deployment stages in the project. This allows users to automated the results of refactoring to some degree in to the project.
We added two new test conditions for Database Unit Tests
- ChecksumCondition – Which you can use to verify that the checksum of the data set returned by a database unit test matches the checksum of an expected data set.
- ExpectedSchemaTestCondition – Which you use to verify that the column names and data types of the returned data set match expected values.

Download page:
http://www.microsoft.com/downloads/details.aspx?FamilyID=73ba5038-8e37-4c8e-812b-db14ede2c354&displaylang=en

Installer download:
http://download.microsoft.com/download/f/b/8/fb8d1c0d-c0c4-4004-ab86-12396b2a3ee3/VSTSDB2008PT.msi

Documentation download:
http://download.microsoft.com/download/f/b/8/fb8d1c0d-c0c4-4004-ab86-12396b2a3ee3/Power Tools 2008.doc

Happy Valentine’s day!

-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

Home of the Data Dude : VS2008

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

Channel 9 VSDB 2008 GDR Interview

VSTS 2008 Database Edition GDR June CTP

What is in the GDR?

Architectural changes

Project System

SQL Server 2008 Support

Build & Deploy

Refactoring

Schema Compare

T-SQL Static Code Analysis

Dependency Viewer

Database Unit Testing

• Data Generation

Public extensibility:

So where to get the GDR?

Feedback, questions, bugs, suggestions

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

Command line SQL Static Code Analysis

Step 0: Install the Power Tools

Step 1: Create a new database project or open an existing one

Step 2: Unload the project

Step 3: Import the Microsoft.VisualStudio.TeamSystem.Data.PowerTools.Tasks.targets file

Step 4: Reload the project

Step 5: Start a "Visual Studio 2008 Command Prompt"

Step 6: Run T-SQL Static Code Analysis from the command-line

Step 7: Look at the results

Step 8: Clean up the results

Conclusion:

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

File Bound Generator

Step 0: Install the Power Tools

Step 1: Create a new project and add a table

Step 2: Create a new Data Generation Plan

Step 3: Create some test input

Step 4: Configure the File Bound Generator

Step 5: Execute the Data Generation Plan

Step 6: Display the results

Conclusion

Apply Test-Driven Development to your Database Projects

Data Generation Wizard

Step 1: Add a new Data Generation plan using the Data Generation Wizard.

Step 2: Launch the Data Generation Wizard

Step 3: Select your source database

Step 4: Run the wizard

Step 5: The resulting data generation plan

Step 6: The resulting column configuration

Step 7: Running the generation plan

Step 8: Showing the results

Tech·Ed 2008 Developers