topology. Each command has an originating server tag on it so it does not
"ChrisR" <ChrisR@discussions.microsoft.com> wrote in message
news:37CA311D-26D6-42A9-88B7-A1396C8CB730@microsoft.com...
>I understand why you would want it to be spread out, but I don't understand
> how it gets spread put. Does the app need to be written a certain way?
>
>
>
> "Hilary Cotter" wrote:
>
>> It's scale out read and write performance. Instead of having 100 users
>> banging away against one box you have two boxes and 50 of the 100 users
>> banging away against box 1 and the other 50 banging away against box 2.
>> You
>> get improved performance because of reduced io contention, lock
>> contention,
>> and improved concurrency.
>>
>> --
>> Hilary Cotter
>>
>> Looking for a SQL Server replication book?
>>
http://www.nwsu.com/0974973602.html >>
>> Looking for a FAQ on Indexing Services/SQL FTS
>>
http://www.indexserverfaq.com >>
>>
>>
>> "ChrisR" <ChrisR@discussions.microsoft.com> wrote in message
>> news:8EB2FFF2-B2A5-4F1A-A0AB-58552D3C212D@microsoft.com...
>> > BOL link:
>> >
>> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/23e7e8c1-002f-4e69-8c99-d63e4100de64.htm
>> >
>> > Howdy all. I was just reading up on this topic and have a question. It
>> > says
>> > on this page (Topology with two participating databases) that reads
>> > will
>> > be
>> > spread out between the two servers, thereby giving better performance.
>> > But
>> > it
>> > doesnt say how that is accomplished. Does the app have to be designed a
>> > specific way, like it would be if updates were going to go between the
>> > two
>> > boxes in the same scenario?
>> >
>> > TIA, ChrisR
>> >
>>
>>
>>