|
What would happen is that all of the servers would be replicated first. All would have the same data. They need to have the same amount of space on them for this to work effectively. Anyway, all servers would have the same data and when something is added, all of the servers have the same access to the same information. The load-balancing comes in to where the "balancer" tells the application which server to route to.
What I would suggest is putting all of the data in one central location, instead of on several different servers. Then, on each of your servers, you have SQL loaded and tell it where the data store is located (NAS or what-have you). The SQL on every server will always pull the same info from the same place, but the SQL server is being load-balanced for how to handle the information.
Data storage would be easy since all you're putting into it is text from SQL. What is power hungry is how what you do with the SQL info, or how MS SQL uses the info. MS SQL is quite a power hungry/memory hungry program.
__________________
"You hear the one about the fella who died, went to the pearly gates? St. Peter let him in. Sees a guy in a suit making a closing argument. Says, "Who's that?" St. Peter says, "Oh, that's God. Thinks he's Denny Crane."
|