Oh yeah... almost forgot... the method I described that uses multiple tables, a constraint, and a view to make a "partitioned" view, is being deprecated. If you have no SQL Server 2000 installations to support in this manner, consider using a "partitioned table", instead. The problem with that is that it won't work on the Standard Edition of SQL Server... you need the Enterprise Edition for production.
I guess that's reason #5 for NOT doing it that way. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.