Scaling out SQL Server 2005

We often hear about scaling up when it comes to our server environments, but what about scaling out?  Scaling out is best described by an excerpt from a new MSDN article published in April:

There are two kinds of scalability: scaleup and scaleout. Scaleup means scaling to a bigger, more powerful server—going from a four-processor server to a 16-processor or 32-processor server, for example. This is the most common way for databases to scale. When your database runs out of resources on your current hardware, you go out and buy a bigger box with more processors and more memory. Scaleup has the advantage of not requiring significant changes to the database. In general, you just install your database on a bigger box and keep running the way you always have, with more database power to handle a heavier load. Scaleout means expanding to multiple servers rather than a single, bigger server. Scaleout usually has some initial hardware cost advantages—eight four-processor servers generally cost less than one 32-processor server—but this advantage is often cancelled out when licensing and maintenance costs are included. In some cases, the redundancy offered by a scaleout solution is also useful from an availability perspective.

You can find out about how SQL Server 2005 can easily scale out - with practical examples when you read the full article which is posted here:

https://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/ScalOutSQL.asp

Comments

• Anonymous
  January 01, 2003
  SQL Server 2005でのScaling Out(SAN経由でReadonly DBを複数SQL Serverから読出)