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 ...

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 ...

How to diagnose problem inside Visual Studio Team System Database Edition is the subject for this blog post. When the product does not behave as expected we might ask you to create a trace of the activity that you are performing and send us the resulting log file. Build-in Tracing VSDB ships with build-in tracing functionality. We ship a ...

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 ...

Visual Studio 2005 Team System Database Professional post Service Release 1 (SR1) roll-up package 1, is now available. For a list of issues that are fixed, please see knowledge base article KB941278. You can download the roll-up from the Microsoft Connect site ...

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 ...

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: ...

Lately we have been getting questions about self-referencing database calls. What I mean with that is that you are referencing SQL objects using a 3-part name while referencing objects that reside inside your current database context. For example: 1: use Northwind 2: go 3:  4: SELECT * FROM Northwind.dbo.Categories 5: go Just ...

When Visual Studio Team System Database Edition opens a design-time validation database, it acquires an exclusive application lock on the DesignDB database using the following code. 1: EXEC @rc = sp_getapplock N'TSDATA', N'Exclusive', N'Session', 0, N'dbo'; .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: ...

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