<p>I'm comparing between two techniques to create partitioned tables in SQL 2005.</p>

<ul>
<li>Use partitioned views with a standard version of SQL 2005 (described <a href="http://www.sqlservercentral.com/articles/SQL+Server+2005/61676/" rel="nofollow noreferrer">here</a>)</li>
<li>Use the built in partition in the Enterprise edition of SQL 2005 (described <a href="http://www.sqlservercentral.com/articles/SQL+Server+2005/61765/" rel="nofollow noreferrer">here</a>)</li>
</ul>

<p>Given that the enterprise edition is much more expensive, I would like to know what are the main benefits of the newer enterprise built-in implementation. Is it just an time saver for the implementation itself. Or will I gain real performance on large DBs?</p>

<p>I know i can adjust the constraints in the first option to keep a sliding window into the partitions. Can I do it with the built in version?</p>

Yes and no. Cases can be linked to each other, but if you're looking for a tree of cases (prerequisites and such), you need FogBugz 7 or later.
If you're using FogBugz 7.3 or greater, you can now use the
Case Dependency Plugin
, which was released in April 2011.