C
Chris Strug
Hi,
I have an SQL Server 2000 database which is linked to an Access MDB file
through an ODBC link. The application is used by around a dozen users with
up to 4 of these adding and updating records at any one time.
It usually works fine but occaisonally, when trying to update records the
application freezes and I get an ODBC timeout error.
To only apparent way to get things started again is to stop and start the
SQL Server Agent on the server.
I'd had the performance monitor running and I can't see any obvious locks -
although I don't know the package too well so I may not have it configured
correctly. In the performance monitor the problem appears to occur at "SET
NO_BROWSETABLE ON" of the "SQL:BATCHCOMPLETED" event class when a user
attempts an update.
The update in question only concerns a a single form linked to a very large
table (30+ columns, 150000+ rows). As I have said, this is an intermittent
problem. Some days its fine, other days it happens every time I start the
Server agent....
Any advice or tips on how to stop this is gratefully received.
Kind thanks
Chris Strug
I have an SQL Server 2000 database which is linked to an Access MDB file
through an ODBC link. The application is used by around a dozen users with
up to 4 of these adding and updating records at any one time.
It usually works fine but occaisonally, when trying to update records the
application freezes and I get an ODBC timeout error.
To only apparent way to get things started again is to stop and start the
SQL Server Agent on the server.
I'd had the performance monitor running and I can't see any obvious locks -
although I don't know the package too well so I may not have it configured
correctly. In the performance monitor the problem appears to occur at "SET
NO_BROWSETABLE ON" of the "SQL:BATCHCOMPLETED" event class when a user
attempts an update.
The update in question only concerns a a single form linked to a very large
table (30+ columns, 150000+ rows). As I have said, this is an intermittent
problem. Some days its fine, other days it happens every time I start the
Server agent....
Any advice or tips on how to stop this is gratefully received.
Kind thanks
Chris Strug