Access Linked Server Breaks

Hi,
1. I have a SQL2000, SP3 Linked Server to an Access mdb that breaks every
couple of weeks. If I do a SELECT statement to the Linked server in Query
Analyzer,, even on a small table of 3 records, QA seems to be working, and
no error messages come up. However, the SELECT command never completes.
2. This problem can always be cured by a reboot of server, but then it
happens again a few days or a few weeks later.
3. This exact same setup worked on another server for 1 3/4 years, but the
problem is on a newly set up SQLServer box.
4. Has anyone experienced such symptoms and found a resolution for sporadic
Linked Server to mdb failures?
5. When a Linked Server connects to an Access mdb, is this being done via an
IP connnection?
I believe a couple of years ago I had viewed the linked server process in
motion, showing among other things some IP connections, but I don't remember
how I did that.
Thanks for any help.
AlanI can't put my finger on it, but this feels like a SQL Server "mem-to-leave"
issue (the portion of SQL Server process memory that is not the buffer
pool.). Linked server info is stored there. Don't know how to help other
than suggesting running DBCC FREEPROCCACHE instead of restarting sql server
(or do you have to reboot the whole box?)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
news:%23SR7gC0PHHA.4280@.TK2MSFTNGP02.phx.gbl...
> Hi,
> 1. I have a SQL2000, SP3 Linked Server to an Access mdb that breaks every
> couple of weeks. If I do a SELECT statement to the Linked server in Query
> Analyzer,, even on a small table of 3 records, QA seems to be working, and
> no error messages come up. However, the SELECT command never completes.
> 2. This problem can always be cured by a reboot of server, but then it
> happens again a few days or a few weeks later.
> 3. This exact same setup worked on another server for 1 3/4 years, but the
> problem is on a newly set up SQLServer box.
> 4. Has anyone experienced such symptoms and found a resolution for
> sporadic Linked Server to mdb failures?
> 5. When a Linked Server connects to an Access mdb, is this being done via
> an IP connnection?
> I believe a couple of years ago I had viewed the linked server process in
> motion, showing among other things some IP connections, but I don't
> remember how I did that.
> Thanks for any help.
> Alan
>|||Kevin,
Thanks very much for your reply.
I will try that next time Linked server breaks.
Whole box has had to be rebooted to cure this.
Regards,
Alan
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:%23n6Vrm7PHHA.992@.TK2MSFTNGP06.phx.gbl...
>I can't put my finger on it, but this feels like a SQL Server
>"mem-to-leave" issue (the portion of SQL Server process memory that is not
>the buffer pool.). Linked server info is stored there. Don't know how to
>help other than suggesting running DBCC FREEPROCCACHE instead of restarting
>sql server (or do you have to reboot the whole box?)
>
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
> news:%23SR7gC0PHHA.4280@.TK2MSFTNGP02.phx.gbl...
>|||You may also want to test SP4...lots of memory leaks were fixed between 3
and 4
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Alan Z. Scharf" <ascharf@.grapevines.com> wrote in message
news:e1YnGx8PHHA.4924@.TK2MSFTNGP05.phx.gbl...
> Kevin,
> Thanks very much for your reply.
> I will try that next time Linked server breaks.
> Whole box has had to be rebooted to cure this.
> Regards,
> Alan
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:%23n6Vrm7PHHA.992@.TK2MSFTNGP06.phx.gbl...
>