"Sue Hoegemeier" wrote:

> Do you mean to improve the network latency? You can't really
> do that - workaround it or reduce the network load, yes but
> not directly impact any network latency. You could look at
> using Openquery instead of 4 part names. You could also look
> at setting the collation compatible option using
> sp_serveroption. You can find more information on this in
> books online under sp_serveroption. And the usual tuning the
> query in terms of just the data you are actually using so
> that you aren't sending unnecessary data across the network.
> You can also find some more linked server performance tips
> at: http://www.sql-server-performance.com/linked_server.asp
>
> -Sue
>
> On Mon, 7 Nov 2005 00:15:46 -0800, Murali
> <Murali@discussions.microsoft.com> wrote:
>
> >Hi there,
> >I have a two Linked servers in a database. One of them is colocated in the
> >same lan and the other server is across the country(California to Florida).
> >We have a dedicated T1's(8 of them) between these two location. I have a
> >stored procedure that decides which server to query the table. when I
> >pointed to the remote server response is really slow.
> >Both database servers are identical hardware and the database(data, indexes
> >..).
> >
> >The Network administrators are saying there might be a latency on the T1's.
> >Is there any settings on SQL to improve the latency when querying remote
> >server.
> >
> >Thanks in advance.
> >-Murali
>