Presents your 
SQL SERVER E-NEWSLETTER for August 27, 2002

<------------------------------------------->

Follow these rules when using partitioned views

An updateable partitioned view is a view based on several member tables
that may or may not reside on the same database and/or server. It's best
to implement on a table that's significantly larger than the rest of the
tables you have on your database. If queries against a table are causing
performance degradation, it may be best to implement a partitioned view.

Partitioned views can separate the data from the one large table into
multiple tables with its own set of data. The optimizer uses the views
definition and the check constraints based on each member table to determine
which table(s) to retrieve the data from, which improves efficiency.

To update data using a partitioned view, the member tables must adhere
to the following rules:

* Each member table must have a primary key on the identical number of columns.
* Default constraints can't be associated with any of the columns of the member table columns.
* Indexes can't be created on any computed column of the member tables.
* Each member table must have the same ANSI_PADDING setting.
* Each member table can be referenced only once in the creation of the partitioned view.

----------------------------------------