<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Home of the Data Dude</title><subtitle type="html">Welcome to the blog where the DataDude talks about SQL Server Data Tools and Visual Studio Database Projects</subtitle><id>http://blogs.msdn.com/b/gertd/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/b/gertd/atom.aspx" /><generator uri="http://telligent.com" version="5.6.50428.7875">Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><updated>2009-03-20T11:46:25Z</updated><entry><title>Schema View for SQL Server Data Tools</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2012/04/02/schema-view-for-sql-server-data-tools.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2012/04/02/schema-view-for-sql-server-data-tools.aspx</id><published>2012-04-02T18:29:47Z</published><updated>2012-04-02T18:29:47Z</updated><content type="html">Today the team released the first version of the SQL Server Data Tools – Power Tools, which adds the ability to navigate the schema of your project inside the SQL Server Object Explorer. Blog post detailing the release: http://blogs.msdn.com/b/ssdt/archive/2012/04/02/first-release-of-ssdt-power-tools.aspx SSDT Power Tools installation location: http://visualstudiogallery.msdn.microsoft.com/9b0228c6-15d1-44de-9279-66dde12bf861?SRC=Featured Please check it out, @DataDude...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2012/04/02/schema-view-for-sql-server-data-tools.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10290047" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>SQL Connections Spring 2012</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2012/03/23/sql_2D00_connections_2D00_spring_2D00_2012.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2012/03/23/sql_2D00_connections_2D00_spring_2D00_2012.aspx</id><published>2012-03-23T21:17:43Z</published><updated>2012-03-23T21:17:43Z</updated><content type="html">Next week, at the SQL Server Connections conference, I will be presenting “Database Development with SQL Server Data Tools”, a 60 minute overview how you can leverage SQL Server Data Tools (SSDT) for your daily database development and deployment tasks. When: Tuesday March 27th 2012, 10:00-11:00AM Abstract: SMS01: Database Development with SQL Server Data Tools Gert Drapers SQL Server Data Tools (SSDT) transforms traditional database development by introducing a declarative, model-based experience...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2012/03/23/sql_2D00_connections_2D00_spring_2D00_2012.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10287085" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>SQL Server Data Tools Released, Available Today!</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2012/03/06/sql-server-data-tools-released-available-today.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2012/03/06/sql-server-data-tools-released-available-today.aspx</id><published>2012-03-07T01:43:07Z</published><updated>2012-03-07T01:43:07Z</updated><content type="html">Today we released the first official release of the “SQL Server Data Tools” (SSDT) to the web. Even though this release accompanies SQL Server 2012 RTM, you can use SSDT against SQL Server 2005 or later, including SQL Azure. So download it now! and get started developing and deploying your SQL Server databases using SQL Server Data Tools....(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2012/03/06/sql-server-data-tools-released-available-today.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10278829" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="SSDT" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SSDT/" /><category term="SQL2012" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQL2012/" /></entry><entry><title>SQL Server Developers Tools code-named “Juneau” becomes SQL Server Data Tools (SSDT)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2011/10/17/sql-server-developers-tools-code-named-juneau-becomes-sql-server-data-tools-ssdt.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2011/10/17/sql-server-developers-tools-code-named-juneau-becomes-sql-server-data-tools-ssdt.aspx</id><published>2011-10-17T19:00:00Z</published><updated>2011-10-17T19:00:00Z</updated><content type="html">Last week at the SQL PASS SUMMIT 2011 in Seattle, Ted Kummert announced during his keynote that the final name of SQL Server Developers Tools code-named “Juneau” will be SQL Server Data Tools or SSDT for short. Additionally, the final name for SQL Server “Denali” will be SQL Server 2012. Besides the final name there were other important data points shared at the PASS Summit regarding SSDT: SSDT will be broadly available as a free component of the SQL Server platform for all SQL Server users. SSDT...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2011/10/17/sql-server-developers-tools-code-named-juneau-becomes-sql-server-data-tools-ssdt.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10226629" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>VSDB Common Pitfalls 1</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2010/12/18/vsdb-common-pitfalls-1.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2010/12/18/vsdb-common-pitfalls-1.aspx</id><published>2010-12-19T02:08:26Z</published><updated>2010-12-19T02:08:26Z</updated><content type="html">Symptom: The resulting database deployment script always creates the database This seems to be a common problem users are struggling with like illustrated by the following set of forum post . A user creates a database project, imports an existing database, builds and deploys. The resulting script always performs a CREATE DATABASE, why? The answer is very simple, by default there is no target database connection defined, the deployment detects this and instead of failing, it assumes the target database...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2010/12/18/vsdb-common-pitfalls-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10106893" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Let’s pick up blogging again…</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2010/12/18/let-s-pick-up-blogging-again.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2010/12/18/let-s-pick-up-blogging-again.aspx</id><published>2010-12-19T01:34:40Z</published><updated>2010-12-19T01:34:40Z</updated><content type="html">Sorry it has been really quiet on this blog for a while now, new job and new projects get in the way. However when going through the MSDN forum for Visual Studio Database Projects it seems there is a need for more hands-on examples and understanding about how the system works and behaves. Besides that it seems that the documentation is either missing, unclear or unread about many things, since it seems that everybody is having to solve many of the problems over and over again. Therefore it seemed...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2010/12/18/let-s-pick-up-blogging-again.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10106890" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>DefaultDataPath</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/11/30/defaultdatapath.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/11/30/defaultdatapath.aspx</id><published>2009-12-01T01:48:10Z</published><updated>2009-12-01T01:48:10Z</updated><content type="html">VSDB uses the the ($DefaultDataPath) SQLCMD variable to represent the location where you would place your data and log file of your database. The deployment engine sets the value of SQLCMD variable by querying SQL Server using the following query: 1: DECLARE @ value nvarchar(512), 
 

 
 2: @rc int ; 
 

 
 3: EXEC @rc = [master].[dbo].[xp_instance_regread] N 'HKEY_LOCAL_MACHINE' ,N 'Software\Microsoft\MSSQLServer\MSSQLServer' ,N 'DefaultData' , @ value output -- , 'no_output'; 
 

 ...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/11/30/defaultdatapath.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9930502" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="tsbt-db" scheme="http://blogs.msdn.com/b/gertd/archive/tags/tsbt_2D00_db/" /><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /></entry><entry><title>SQL Server 2008 R2</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/11/24/sql-server-2008-r2.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/11/24/sql-server-2008-r2.aspx</id><published>2009-11-24T21:26:20Z</published><updated>2009-11-24T21:26:20Z</updated><content type="html">Now that SQL Server 2008 R2 November CTP is available, I found some time to install it and test the existing Visual Studio 2008 Team System Database Edition GDR R2 release with it. The only thing that is really different from a SQL Server point of view besides two changes to the SQL parser, is that the version number changed from 10.00.xxxx to 10.50.yyyy (10.00.2531 for the November CTP). As we will see enough to confuse the VSDB 2008 GDR R2 release. First step, is to create a connection inside Solution...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/11/24/sql-server-2008-r2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9928240" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="SQL2008R2" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQL2008R2/" /></entry><entry><title>Pre and Post Deployment Events</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/10/13/pre-and-post-deployment-events.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/10/13/pre-and-post-deployment-events.aspx</id><published>2009-10-13T21:33:39Z</published><updated>2009-10-13T21:33:39Z</updated><content type="html">Visual Studio makes it relatively easy to hook in to pre and post build events, by using the Project properties tab named Build Events. However when using Database Projects (.dbproj) you more often need to do something at deployment time. The good news is that the standard MSBuild framework, already defines these events, the bad news is that you manually have to update the project file yourself. The steps are pretty simple: Unload the project, by right clicking on the project node inside Solution...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/10/13/pre-and-post-deployment-events.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9906849" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="Deploy" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Deploy/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="MSBuild" scheme="http://blogs.msdn.com/b/gertd/archive/tags/MSBuild/" /></entry><entry><title>Pre-Deployment Scripts</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/09/14/pre-deployment-scripts.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/09/14/pre-deployment-scripts.aspx</id><published>2009-09-14T23:48:00Z</published><updated>2009-09-14T23:48:00Z</updated><content type="html">Pre-deployment script do not change the outcome of deployments! The above statements is something that most users do not realize when using pre-deployment scripts. Since the pre-deployment script is included in to the deployment script, it therefore by definition runs after the comparison the the source model with the target database (model), and therefore cannot change the behavior of the deployment. For example: If you know you have an orphaned object that is blocking a certain upgrade scenario...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/09/14/pre-deployment-scripts.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9895130" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="Deploy" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Deploy/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="MSBuild" scheme="http://blogs.msdn.com/b/gertd/archive/tags/MSBuild/" /></entry><entry><title>NESQL Presentation – Declarative Database Development</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/09/14/nesql-presentation-declarative-database-development.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/09/14/nesql-presentation-declarative-database-development.aspx</id><published>2009-09-14T21:57:03Z</published><updated>2009-09-14T21:57:03Z</updated><content type="html">Last week, September 10, I was invited by the New England SQL Server User Group to present about my favorite topic “ Declarative Database Development ”. I posted the slides of the presentation at DBProj.com . GertD @ www.DBProj.com...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/09/14/nesql-presentation-declarative-database-development.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9895094" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="Declarative Database Development" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Declarative+Database+Development/" /></entry><entry><title>MyDevConnections Volume 2 issue 1</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/09/09/mydevconnections-volume-2-issue-1.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/09/09/mydevconnections-volume-2-issue-1.aspx</id><published>2009-09-10T06:26:43Z</published><updated>2009-09-10T06:26:43Z</updated><content type="html">The DevConnections conference organization (Tech Conferences Inc.), just released the latest issue of the magazine accompanying the conferences, named: MyDevConnections . In this edition (volume 2, issue 1) you will find an article that I wrote about “Declarative Database Development – Define What You Want, Not How You Get There!” (see page 68-71). If you did not receive the printed edition of the magazine, don’t worry since you can download the PDF version. During the Spring 2009 SQL Connections...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/09/09/mydevconnections-volume-2-issue-1.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9893444" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="DevConnections" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DevConnections/" /><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="Declarative Database Development" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Declarative+Database+Development/" /></entry><entry><title>SqlCmdVars.exe</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/08/01/sqlcmdvars-exe.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/08/01/sqlcmdvars-exe.aspx</id><published>2009-08-02T03:46:53Z</published><updated>2009-08-02T03:46:53Z</updated><content type="html">This post announces the availability of a small helper utility that will allow you to maintain your database.sqlcmdvars files from a command line tool. Description: What is the scenario? If you are using vsdbcmd.exe to deploy your schema, you include the Database.sqlcmdvars, however vsdbcmd.exe does not have an option to override the values of the SQLCMD variables used at the command line level like you can do when using MSBuild (assuming you chained the SQLCMD variable to a MSBuild property). This...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/08/01/sqlcmdvars-exe.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9855399" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="SQLCMD" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQLCMD/" /></entry><entry><title>VSDB 2008 Version Numbers</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/07/29/vsdb-2008-version-numbers.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/07/29/vsdb-2008-version-numbers.aspx</id><published>2009-07-30T01:37:42Z</published><updated>2009-07-30T01:37:42Z</updated><content type="html">We frequently get asked how to identify the version a user is running with, so here is the list of Visual Studio Team System 2008 Database Edition releases. The information is retrieved using Help =&amp;gt; About Microsoft Visual Studio inside the Visual Studio shell (devenv.exe). Alternatively you can copy the information to the clipboard using the “Copy Info” button. &amp;#160; When you are on the latest versions it should look like this: &amp;#160; Release Visual Studio version information Database Edition...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/07/29/vsdb-2008-version-numbers.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9852623" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="SETUP" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SETUP/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="Troubleshooting" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Troubleshooting/" /></entry><entry><title>VSDBCMD.EXE Return Codes</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx</id><published>2009-07-21T23:09:31Z</published><updated>2009-07-21T23:09:31Z</updated><content type="html">Quick one based on a forum question where somebody asked how to detect if VSDBCMD.EXE failed or succeeded inside a batch file. VSDBCMD.EXE does not return a very elaborate amount of information, there are just two return values 0 and 1, where zero indicates success and 1 failure. So in order to test for this you simply check the ERRORLEVEL inside your batch file. This is a simple wrapper that I use that shells out to VSDBCMD.EXE and passes all the parameters, so I do not have to place the Deploy...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9843792" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="vsdbcmd" scheme="http://blogs.msdn.com/b/gertd/archive/tags/vsdbcmd/" /></entry><entry><title>Agile Database Techniques</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/07/08/agile-database-techniques.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/07/08/agile-database-techniques.aspx</id><published>2009-07-09T03:16:52Z</published><updated>2009-07-09T03:16:52Z</updated><content type="html">I am happy to announce that there is a new class dedicated to VSDB. “ Agile Database Techniques ”, is a 3-days course that provides students with the knowledge and skills to properly manage the SQL Server database development lifecycle in an agile environment. You will learn how to manage changes to the database structure, ensuring quality through T-SQL unit testing, and how to automate the building and deploying of SQL Server databases. Intended for developers and administrators already comfortable...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/07/08/agile-database-techniques.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9825152" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Assigning MSBuild Properties to SQLCMD Variables</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/06/21/assigning-msbuild-properties-to-sqlcmd-variables.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/06/21/assigning-msbuild-properties-to-sqlcmd-variables.aspx</id><published>2009-06-22T02:21:44Z</published><updated>2009-06-22T02:21:44Z</updated><content type="html">I am receiving the following question a lot: How do I propagate MSBuild properties to SQLCMD variables. In order to make the Visual Studio 2008 Team System Database Edition GDR release use the data from an MSBuild property inside a SQLCMD variable you need to do three things: Add the variable to the Database.sqlcmdvars file Add a XML fragment to the database project (.dbproj) file Use the SQLCMD variable First you need to add a SQLCMD variable to the Database.sqlcmdvars file, in this example we will...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/06/21/assigning-msbuild-properties-to-sqlcmd-variables.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9796461" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="MSBuild" scheme="http://blogs.msdn.com/b/gertd/archive/tags/MSBuild/" /><category term="SQLCMD" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQLCMD/" /></entry><entry><title>DBSchema file for SQL LiteSpeed XP’s</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/06/10/dbschema-file-for-sql-litespeed-xp-s.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/06/10/dbschema-file-for-sql-litespeed-xp-s.aspx</id><published>2009-06-11T03:10:38Z</published><updated>2009-06-11T03:10:38Z</updated><content type="html">Based on a customer request I created a .dbschema file which contains the definitions of all the extended stored procedures used by SQL LiteSpeed 5.0 that live inside the master database. Since schema import does not import the definition of extended stored procedures, the user could no resolve the reference to the extended stored procedures. The following 39 extended stored procedures are defined inside the dbschema file: Extended Stored Procedure name [dbo].[xp_append_file] [dbo].[xp_backup_database...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/06/10/dbschema-file-for-sql-litespeed-xp-s.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9725404" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="tsbt-db" scheme="http://blogs.msdn.com/b/gertd/archive/tags/tsbt_2D00_db/" /><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="DatabaseReferences" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DatabaseReferences/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /><category term="DBSchema" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBSchema/" /></entry><entry><title>System Objects in TEMPDB</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/06/10/system-objects-in-tempdb.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/06/10/system-objects-in-tempdb.aspx</id><published>2009-06-11T02:17:09Z</published><updated>2009-06-11T02:17:09Z</updated><content type="html">Today a user send me a question how to resolve reference of system objects inside tempdb? My first thought was this should get resolved by loading the master.dbschema file. However this did not resolve the issue, so time to ask for an example, which slightly altered looks something like this: 1: CREATE PROC [dbo].[testproc] 

 2: AS 

 3: SET NOCOUNT ON 

 4: -- code simplified for this example 

 5: SELECT [object_id], 

 6: [name] 

 7: FROM [tempdb].[sys].[objects] 
 


 When you...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/06/10/system-objects-in-tempdb.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9725274" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Declarative Database Development</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/06/05/declarative-database-development.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/06/05/declarative-database-development.aspx</id><published>2009-06-06T01:58:36Z</published><updated>2009-06-06T01:58:36Z</updated><content type="html">Define What You Want, Not How You Get There! &amp;#160; If Not Exists… Database development is many aspects behind in comparison to regular application development. If you look how database development is integrated with regular application development or development processes it becomes even more obvious that there is room for improvement in this area. When asked, you will find that many database developers are spending their valuable time writing, maintaining, and testing database deployment scripts...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/06/05/declarative-database-development.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9702216" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="tsbt-db" scheme="http://blogs.msdn.com/b/gertd/archive/tags/tsbt_2D00_db/" /><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="Declarative Database Development" scheme="http://blogs.msdn.com/b/gertd/archive/tags/Declarative+Database+Development/" /><category term="DBProj.com" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DBProj-com/" /></entry><entry><title>RTM of VSDB 2008 GDR R2</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/04/22/rtm-of-vsdb-2008-gdr-r2.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/04/22/rtm-of-vsdb-2008-gdr-r2.aspx</id><published>2009-04-22T18:32:12Z</published><updated>2009-04-22T18:32:12Z</updated><content type="html">The QFE rollup release for the Visual Studio Team System 2008 Database Edition GDR release is now available. You can download the SETUP.EXE from the regular location. ( http://www.microsoft.com/downloads/details.aspx?FamilyID=bb3ad767-5f69-4db9-b1c9-8f55759846ed ) If you have the VS2008 RTM version of the Database Edition or the RTM version of the VSDB 2008 GDR release installed, this setup will automatically upgrade your installation. If you have the RC installed of the QFE rollup, you have to uninstall...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/04/22/rtm-of-vsdb-2008-gdr-r2.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9562506" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="tsbt-db" scheme="http://blogs.msdn.com/b/gertd/archive/tags/tsbt_2D00_db/" /><category term="VSDB" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB/" /><category term="QFE" scheme="http://blogs.msdn.com/b/gertd/archive/tags/QFE/" /></entry><entry><title>Release Candidate of GDR QFE</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/03/26/release-candidate-of-gdr-qfe.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/03/26/release-candidate-of-gdr-qfe.aspx</id><published>2009-03-27T04:31:16Z</published><updated>2009-03-27T04:31:16Z</updated><content type="html">Yesterday, March 25th, the development team released an RC of the upcoming QFE of the Visual Studio 2008 Team System Database Edition GDR bits. I was surprised to read the new naming “ Visual Studio 2008 Database Edition GDR v2 RC1 ”. Anyhow what is in a name? It is about the content if you would ask me. This RC contains many important fixes for issues that users have reported since the release in November 2008. &amp;#160; Fixes in this RC release Schema Validation Aliased external objects do not resolve...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/03/26/release-candidate-of-gdr-qfe.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9512606" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /><category term="QFE" scheme="http://blogs.msdn.com/b/gertd/archive/tags/QFE/" /></entry><entry><title>SQL Connections Slides and Demo Posted</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/03/26/sql-connections-slides-and-demo-posted.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/03/26/sql-connections-slides-and-demo-posted.aspx</id><published>2009-03-26T23:55:54Z</published><updated>2009-03-26T23:55:54Z</updated><content type="html">It was great to be able to meet many new users of the Database Edition product at the SQL Connection Spring 2009 conference this week. Thank you for attending the sessions. There were lots of great questions, critical feedback and input for new features and improvements, they are all noted! As promised the slides and demos of the two “DataDude” sessions are now posted on the www.DBProj.com website. SDB413: Automating Database Deployment Do you have a need to automate the deployment of your database...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/03/26/sql-connections-slides-and-demo-posted.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9511943" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="SQLConnections" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQLConnections/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /></entry><entry><title>DBPROJ vs. DBP</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/03/25/dbproj-vs-dbp.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/03/25/dbproj-vs-dbp.aspx</id><published>2009-03-25T15:52:09Z</published><updated>2009-03-25T15:52:09Z</updated><content type="html">Can the “real” database project please identify itself? Life can be confusing and we did not help you making it much easier by having two types of Database Projects inside Visual Studio. For the longest time there has been a “Database Project” inside Visual Studio. This project type has the file extension of .DBP and is available under the Other Project Types\Database\Database Project node inside the New Project dialog. It has not evolved for many releases and is purely there for legacy support....(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/03/25/dbproj-vs-dbp.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9507703" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author></entry><entry><title>Up to SQL Connections Spring 2009 (Orlando, FL)</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/b/gertd/archive/2009/03/20/up-to-sql-connections-spring-2009-orlando-fl.aspx" /><id>http://blogs.msdn.com/b/gertd/archive/2009/03/20/up-to-sql-connections-spring-2009-orlando-fl.aspx</id><published>2009-03-20T21:46:25Z</published><updated>2009-03-20T21:46:25Z</updated><content type="html">Next week I will be presenting at SQL Connections in Orlando where I will be covering some fun topics on DataDude and general SQL Server. Here is the list. SQL Connections Spring 2009 (Orlando, FL) SDB413: Automating Database Deployment Do you have a need to automate the deployment of your database schema? Learn how to leverage DBSCHEMA files in combination with the command line VSDBCMD.EXE deployment engine. The latest Visual Studio 2008 Team System Database Edition GDR release provides a redistributable...(&lt;a href="http://blogs.msdn.com/b/gertd/archive/2009/03/20/up-to-sql-connections-spring-2009-orlando-fl.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9493170" width="1" height="1"&gt;</content><author><name>Gert Drapers (MSFT)</name><uri>http://blogs.msdn.com/gertd/ProfileUrlRedirect.ashx</uri></author><category term="DevConnections" scheme="http://blogs.msdn.com/b/gertd/archive/tags/DevConnections/" /><category term="SQLConnections" scheme="http://blogs.msdn.com/b/gertd/archive/tags/SQLConnections/" /><category term="VSDB2008GDR" scheme="http://blogs.msdn.com/b/gertd/archive/tags/VSDB2008GDR/" /></entry></feed>