Distributed Partitioned Views | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Distributed Partitioned Views

According to this Features by Edition comparison Distributed Partitioned Views are supported only in SQL Server 2000 Enterprise Edition. However, creating a partitioned view Creating a Partitioned View is pretty straightforward – one has to:
(1) add linked server definitions on each member server,
(2) set the lazy schema validation option, using sp_serveroption, for each linked server definition,
(3) create a view with UNION ALL clause on each member server. Each of the above steps can be performed on a machine running Standard Edition of SQL Server, so why do I need Enterprise Edition to use Distributed Partitioned Views feature?Rediscover the web
http://www.mozilla.org/firefox/

As distributed partitioned views involves the setting up Federated servers for the large database and is not a quick task, the performance gains produced by Distributed Partitioned Views on large tables can make it more than worth while, and this can be well supported and managed in Enterprise Edition as it is configured to optimum levels as compared to Standard edition. One of the MS article refers:
Distributed Partitioned Views is made possible through the implementation of shared-nothing clustering technology. The shared-nothing approach to clustering is generally considered superior to the shared-disk approaches, because single points of failure and bottlenecks due to shared resources do not occur. In SQL Server 2000, shared-nothing clustering is implemented as a group, or federation, of independently administered servers that cooperate to manage workload jointly. This is a tremendous step toward a centrally-managed, shared-nothing offering, with the same level of performance. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I don’t fully understand. I’d be grateful for further explanations.
quote:Originally posted by satya As distributed partitioned views involves the setting up Federated servers for the large database and is not a quick task, the performance gains produced by Distributed Partitioned Views on large tables can make it more than worth while, and this can be well supported and managed in Enterprise Edition as it is configured to optimum levels as compared to Standard edition.
Do you mean that it is possible to set up distributed partitioned views in Standard Edition, although they perform better in Enterprise Edition?
quote:Originally posted by satya One of the MS article refers:
Distributed Partitioned Views is made possible through the implementation of shared-nothing clustering technology.
Is it necessary to set up a cluster of servers to use distributed partitioned views? — Rediscover the web
http://www.mozilla.org/firefox/

I mean to compare the advantages of EE over SE and when using Distributed partitioned views SE is limited and not allowed to use distributed transactions effectively, as compared to EE. In this case Federated Database Server are supported in EE and not in SE. The most important aspect of distributed partitioned view performance is minimizing the amount of data transferred between member servers. Cluster setup is not required, in this case linked server concept will work. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I have just read very thoroughly the description of the Distributed Partitioned Views feature and I guess that the sentence below is what I’ve been looking for: The SQL Server 2000 query processor contains a number of enhancements so that these views can be updated, and increase performance when doing distributed queries to pull data from other member servers. It doesn’t say that literally but I might guess that those enhancements can be found only in EE. — Rediscover the web
http://www.mozilla.org/firefox/

EE has upper hand than SE in deciding the optimization of using system resources. SO for the subject and many refers to use EE than SE to get optimum performance and less hassle. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>