Skip to main content

  • Scaling Out SQL Server 2005

    out data that must be updated, but that still has a relatively low update
    frequency, is often best handled by replication. Instead of several database
    engines accessing a single copy of the database, you have multiple copies of the
    database, so that each database engine maintains its own copy. This option
    provides scaleout, while also allowing updates to the data. Replication is used
    to propagate changes to all copies of the data. Figure 2 illustrates the use of
    Peer-to-Peer replication as a scaleout solution.

    msdn.microsoft.com/...aa479364.aspx - Preview

    SQL Server Clustering on 2009-04-08

1 - 1 of 1
Showing 20 items per page
List Comments (0)