Linked Servres and deadlocks

We are running a SQL 2000 production server with MSDE 2000 clients for local
storage. The 60+ clients are set up as linked servers back to the productio
n server. The application calls stored procedures on the client that referen
ce back to the linked serve
r. During these procedure calls we experience a high number of deadlocks, a
lot more than similar procedures running directly on the server. I'm looking
for documentation/ help on such scenarios.
Thanks in Advance
Paul G.Hi Paul,
Sounds like you have a hot spot in database and your will first need to iden
tify, which object(s) are causing problem. You may want to run sp_lock on s
erver to locate "Wait" in status column and note objectid. Overall, you will
need to understand your ap
plication and how it works. Things to consider:
1. Indexing
2. Network speed between clients and server
3. Long running queries - may need to modify Connections Timeout and Query T
imeout values
If you are really stuck, please email me and we can work together to pin-poi
nt issue
Cheers,
Phillip MacPherson
SQL Server Consultant DBA (MCP)

server vs Advantage Local Server

I'm trying to define a linked server (from within SQL Server 2005
Express) to an Advantage Local Server.
Using OpenQuery, I get error message:
Cannot create an instance of OLE DB provider 'Advantage.OLEDB' for
linked server 'LStest'
A linked server to an Advantage Database Server (remote) works fine. Is
there a way to make it works locally?
Thanks a lot in advance for help,SQL Server Standard works fine...
"rcloutie" wrote:
> I'm trying to define a linked server (from within SQL Server 2005
> Express) to an Advantage Local Server.
> Using OpenQuery, I get error message:
> Cannot create an instance of OLE DB provider 'Advantage.OLEDB' for
> linked server 'LStest'
> A linked server to an Advantage Database Server (remote) works fine. Is
> there a way to make it works locally?
> Thanks a lot in advance for help,
>