May 15, 2012 at 2:28 pm
What we are doing?
We are developing a distributed service broker application that processes data on different databases residing on different servers. These service broker applications are deployed are interdependent. These service broker applications process business routines (TSQL statements) on receiving a message from another service broker application. Basically we are going to configure a load balancing configuration as mentioned your book. All the data generated as a result of processing service broker applications are saved locally on each server.
What we want to achieve?
Synchronize/transfer data to a single Master database. There may be 5-10 huge tables and may not be all the tables in the database.
Questions
1. Which is a more viable technology SSIS or replication and why?
2. Are there any other data transfer alternatives to SSIS or replication for the above mentioned scenario?
3. Also since Load balancing configuration is prettymuch a deterministic routing and not a actual load balancing is there a way to actually load balance the work load based on availability of server resources i.e. we are having servers with different configurations some are very high end server and other are mediocre servers.
Thanks a lot.
~ Jagadish
May 16, 2012 at 2:41 pm
Please do not cross-post, it just fragments replies and wastes people's time. Direct all replies here:
http://www.sqlservercentral.com/Forums/Topic1300592-1281-1.aspx
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply