"James" <jamesdfriesen@hotmail.com> wrote in message
news:1142885711.716158.206300@v46g2000cwv.googlegroups.com...
> Hi,
>
> I have the following situation and would like some advise.
> I am using SQL server 2005. I have smart clients access the database
> over the internet through web services.
>
> I currently have 1 data warehouse type database. It contains about 95%
> read only data which is apended to nightly.
>
> Since the queries are long and complex running on millions of rows of
> data, queries are run asyncronously. I use Service Broker to queue and
> run the queries.
>
> I have the following read/write tables in the database:
> A table to store the results of the queries.
> A table to store the status of the request. Front the front end, I can
> see if the query is queued, running or completed.
> Since the query request itself is very complex, I store the request in
> a series of other tables before the request is queued.
>
> Now, for scalability reasons they want to go to 2 database servers,
> allowing more requests to be run at the same time. Obviously, in
> regards to the read/write tables described above, I need to somehow
> replicate the data between the servers. Any thoughts as to which
> replication method would best fit my scenario?
>
> Any thoughts would be appreciated.
>
> Thanks in advance
> James
>