Cached Data to Linked Server

I have SQL Server 7.0 set up to access a flat file FoxPro database sitting
on an NFS mount (using Services For Unix) as a linked server. Basic
functionality is working great, but I have a couple of nagging problems I'd
like to get solved before I move this into production.
One is that SQL Server seems to cache the FoxPro database for around 5
minutes if there's no activity, possibly longer (or forever?) if the FoxPro
database is being queried. I'm using a stored procedure to run a SELECT *
FROM OPENQUERY() if that makes a difference....
Also, if the NFS server is down and not responding, SQL doesn't timeout for
92 seconds. I've tried setting "remote login timeout", but it doesn't seem
to have any effect. If I set "remote query timeout", then OPENQUERY tells me
it can't set an OLEDB property.
Any ideas?
mbrackett@.bsd.ufl.edu
I don't believe that SQL Server does any caching for the data from a linked
server. You can specify a timeout value for connections to a linked server
by using the sp_serveroption stored procedure in conjunction with the
'connect timeout' option.
Michael Otey
"Mark Brackett" <mbrackett@.bsd.ufl.edu> wrote in message
news:eE9qWxFaEHA.4052@.TK2MSFTNGP10.phx.gbl...
> I have SQL Server 7.0 set up to access a flat file FoxPro database sitting
> on an NFS mount (using Services For Unix) as a linked server. Basic
> functionality is working great, but I have a couple of nagging problems
I'd
> like to get solved before I move this into production.
> One is that SQL Server seems to cache the FoxPro database for around 5
> minutes if there's no activity, possibly longer (or forever?) if the
FoxPro
> database is being queried. I'm using a stored procedure to run a SELECT *
> FROM OPENQUERY() if that makes a difference....
> Also, if the NFS server is down and not responding, SQL doesn't timeout
for
> 92 seconds. I've tried setting "remote login timeout", but it doesn't seem
> to have any effect. If I set "remote query timeout", then OPENQUERY tells
me
> it can't set an OLEDB property.
> Any ideas?
> mbrackett@.bsd.ufl.edu
>