On the load balancing problem of SQL Server _mssql

As of the SQL Server 2008 R2 version, Microsoft has not yet launched an official load-balancing component that can be DIY only through other technical features of SQL Server or by using Third-party components.

In previous articles, the small series also summarized some common "SQL Server cluster" SQL Server Data Synchronization "SQL Server Failover" ... and other related implementation techniques. It's not a very detailed explanation today.

Today I would like to recommend that you try to use third party components and tools, typically a icx database route. Of course, I am not familiar with the manufacturers of these tools, so this article is obviously not advertising. Oh.

For a long time, the SQL Server database server has only "hot standby" solutions and no "load balancing" and "cluster" solutions. While this solution improves the reliability of the system, there are some problems:

* In the face of large amount of data and a large number of database query requests, can only take the vertical upgrading of the server level, while the cost of vertical ascension is much higher than the horizontal expansion.

* In hot spare time, the database server only one is working, the other is in the state of idle backup, resulting in a waste of investment.

* Non-real-time switching.

The emergence of database router software icx provides a better clustering solution for the database system based on MS SQL Server. It can really implement the SQL Server number

According to the library server dynamic load balancing, improve performance and speed; it can truly ensure that the SQL Server database server uninterrupted service, in the event of a server failure in real-time switching to other servers to continue to provide services, switching time to "0".

The database router is a real-time concurrent database transaction synchronization replicator and a load balancer.

Database Router--icx (meaning: I = X database SERVERS), that is, you can connect n databases at the same time after ICX.

1. All database clients access the database through ICX. when accessing and querying SQL Server databases, ICX can allocate servers to provide services according to actual situation, greatly improve service speed and optimize performance, and complete load balancing.

2. ICx can connect multiple databases at the same time (2-16 units, the specific number of units to see the specific needs of customers), the contents of these databases at any time by the ICx guarantee is the end

All the same. In other words, ICx uses a new method of concurrent transaction processing to replicate transactions to the connected N database, making the system have multiple consistent

The most recent logical database DataSet. When one of the database servers fails, ICX can switch to other servers in real time and continue to provide services. Real

To achieve zero-time server switching, greatly improve security, the real meaning of the implementation of server uninterrupted service.