User-defined Triggers may cause performance, connectivity and data integrity issue with Team Foundation Server

I have been seeing see latency and performance problems in couple of scenarios, specifically while performing branching and merging


When you run the TFS BPA tool, you may see an error message similar to the one provided below:
The SQL database "TfsIntegration" contains a trigger named "some trigger name". 


Triggers in some TFS databases can cause connectivity or performance issues. Please do a full backup of your TFS databases and then drop any triggers that are not created by the TFS installation.

Later we found that users should never add user-defined triggers to TFS databases or tables. Triggers can cause connectivity, performance, and data integrity issues. 

Hence, one must use the following guidelines to avoid such issues. 


The TFS databases or tables should not have any triggers.   Prior to deleting any triggers, you should have full backups of all of your TFS databases from the same point in time.



1.     Open SQL Server Management studio and connect to the SQL database engine hosting your TFS databases.

2.    Click on the plus sign to expand databases.

3.     Expand the “TFS...” named database.

4.     Expand programmability.

5.     Click on database triggers.

This will show any triggers in the right-hand reading pane. If there are any present, delete them.



Author: Nitish Nagpal

Reviewed by: Wendell Phillips

Comments (0)

Skip to main content