Does a non-distributed paritioned view make sense? Say for example you have a table with a billion Orders. Orders have a DateTime, Description, Id, etc. There are say, 500 million records in the Orders table. The Orders table is clustered on DateTime, Id. Will splitting it up into seperate tables on the same server, in the same database and horizontally partitioning on the DateTime by month-year increase performance? (Say the month-year partitioning results in member tables that are each 50 million records in size.) If you could go into detail of why/why-not I'd appreciate it. My hunch is no. That as long as the DateTime is the first thing in your Where clause (SQL Server 2000 btw), the partitioned view is nothing more than a "second order cluster" since all source tables are on the same server, in the same database. Am I wrong?