Linked Server CPU hog?

We currently use linked servers at our location for our main SQL server to
link to Oracle, other SQL servers and a remote DB2 (via Informix driver) via
linked servers.
Our DBA has just informed us that he will be cutting all linked servers in
due course as they are causing a CPU problem.
In a nutshell, we were told, that when a transaction across a linked server
connection fails, it also appears to hold open the connection and continues
to use resources that can only be reclaimed by restarting the server.
We currently have SQL2K SP4 installed and are due to go to SQL2K5 later this
year.
Has anyone else come across this problem by chance? Is there a resolution in
2K or has it been resolved in 2K5.
Any information would be of value as we are currently faced with re-writing
our applications that use the linked servers.
Thanks,you use msdtc?
use tg4sql?
why transation fail?
Aleksandar Grbic
"Logicalman" wrote:
> We currently use linked servers at our location for our main SQL server to
> link to Oracle, other SQL servers and a remote DB2 (via Informix driver) via
> linked servers.
> Our DBA has just informed us that he will be cutting all linked servers in
> due course as they are causing a CPU problem.
> In a nutshell, we were told, that when a transaction across a linked server
> connection fails, it also appears to hold open the connection and continues
> to use resources that can only be reclaimed by restarting the server.
> We currently have SQL2K SP4 installed and are due to go to SQL2K5 later this
> year.
> Has anyone else come across this problem by chance? Is there a resolution in
> 2K or has it been resolved in 2K5.
> Any information would be of value as we are currently faced with re-writing
> our applications that use the linked servers.
> Thanks,
>