<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Growing TFS databases</title><link>http://blogs.msdn.com/b/bharry/archive/2011/05/31/growing-tfs-databases.aspx</link><description>I’ve seen a few reports lately of TFS customers whose databases were growing very rapidly.&amp;#160; After investigation, it has often turned out to be that they were uploading a lot of large attachments to TFS as part of their testing process and then not</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Growing TFS databases</title><link>http://blogs.msdn.com/b/bharry/archive/2011/05/31/growing-tfs-databases.aspx#10174863</link><pubDate>Wed, 15 Jun 2011 15:22:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10174863</guid><dc:creator>Brian Harry MS</dc:creator><description>&lt;p&gt;The reason is that these foreign key constraints impose significant performance overhead. &amp;nbsp;Everytime you update a row, seeks must be performed to validate foreign keys and TFS is an unusually write heavy app. &amp;nbsp;We take the approach of encapsulating our databases behind our middle tier (not allowing any untested access paths) and then testing our middle tier very thoroughly to ensure we never violate integrity. &amp;nbsp;I&amp;#39;m not saying that we NEVER miss anything but it&amp;#39;s pretty rare.&lt;/p&gt;
&lt;p&gt;Brian&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10174863" width="1" height="1"&gt;</description></item><item><title>re: Growing TFS databases</title><link>http://blogs.msdn.com/b/bharry/archive/2011/05/31/growing-tfs-databases.aspx#10171649</link><pubDate>Mon, 06 Jun 2011 14:39:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10171649</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;We reported this issue over a year ago. As a well as various TFS database integrity issues (this is the recent one: &lt;a rel="nofollow" target="_new" href="http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/0f8ee76d-0ff5-424b-8170-235477762c9c"&gt;social.msdn.microsoft.com/.../0f8ee76d-0ff5-424b-8170-235477762c9c&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I kee pasking this question over and over again but get no answer: why does TFS database not enforce any data integrity (there is basically no foreing key constraints)?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10171649" width="1" height="1"&gt;</description></item></channel></rss>