Advice in SQL On-Line help, informs that Partioned Views are now Deprecated in SQL 2005 and use of Partioned Tables Advised. Our 'Enterprise' Software Supplier has Client-Server JAVA + Server-Side JAVA [ajax] - forget about their 'C' apps! They are moving to S-S JAVA, slowly leaving C-S-JAVA as legacy. C-S-JAVA -> We, manually, create Custom Tables [_x] against Main Tables eg. [dbo].[traders] and [dbo].[traders_x] with one to one row match using keys/constraints, and add table into CustomFieldDefinitions.xml. S-S-JAVA -> They have retained Main Table [traders] and supplied 2 custom tables where we can add our custom fields: [dbo].[customer_custom] and [dbo].[supplier_custom], though an automatic DataEntity application, there is no entry required in CustomFieldDefinitions. Split based is on traders.tradertype field. Because of our heavy 'bespoke' of C-S-JAVA, some applications cannot, yet, be upgraded to preferred S-S-JAVA. Our software supplier's solution to running both JAVA methodsi tandem using custom tables is: Drop [_x] table eg. traders_x and replace with: Create VIEW traders_x [we must use same name to work with CustomFieldDefinitions] as select id,tradertype,UDFcol1, UDFcol2,.....FROM customers_custom UNION ALL select id,tradertype,UDFcol1, UDFcol2,.....FROM suppliers_custom GO And USE 'INSTEAD OF' TRIGGERS on VIEW to maintain new customers/suppliers_custom tables. I don't need any TRIGGERS on [_custom] Apart from NO Indexing which slows C-S-J apps down even more, this also us to migrate to S-S-J as our 'bespoke' is applied! QUESTION: HOW DOES A PARTIONED TABLE HELP ME if I can't use a Partioned VIEW ?? Yes, I can write a plethoral of triggers to synchronise 'old' _x as a TABLE and 'new' _custom(s), Also Indexing will be allowed!