Geek Answers Handbook

Help me choose which SQL Server 2008 scaling solution to choose (replication, ...)

I am currently moving on to the jungle of SQL Server scaling technologies such as replication, logging, mirroring ... I have the following limitations of my choice:

  • I want read-only downloads to be distributed across the primary and secondary (mirror, subscriber) server
    • Load loading can be sent directly to the main server
    • The solution should be practically free. Schema changes should simply be replicated to the secondary server (note: replication has some serious limitations here, as it seems)
    • Written data should be available very quickly (in less than 1 second, but would be better instantly) on a secondary server
    • If the server crashes, I can easily lose up to one hour of data loss. I'm more interested in simple scalability

Here are a few options for what I could choose: http://msdn.microsoft.com/en-us/library/bb510414.aspx . Any experience you could share?

+5
source share
1 answer

, . SQL Server () . master-slaves . master-master . , , .

- - , , MySpace .

( , , , , ) nosql, (Cassandra, HBase, MongoDB).

, - , () , . , , , , , .

+5

More articles:


All Articles