parissa_bakhshi (11/4/2010)
... use table partiotionning to break your database into parts and put each part in an one cluster node.Now what you have is 3 servers, each of them servicing one part of database.Is that false?
mmhhh... technically this is not what table partitioning means, the generally accepted mean of it is that when you partition a table all partitions remain in the same database. Table partitioning is not a high availability feature.
On the other hand I think you are actually refering to database sharding which is the technique of breaking a database into pieces - by the way, clustering is not even needed. This is not applicable for all databases, an applicable example would be a database serving a search engine. If you want to pursue this path you may want to research "SQL Server Federated Databases".
Hope this helps.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.