Q

Stop MS Access from causing timeouts

Five months ago we migrated our SQL Server databases from 7.0 to 2000. Since then we have experienced timeouts very often. Sometimes we've detected that MS Access blocks the server, and when we kill the process everything starts to work properly. Our server has 3 GB of RAM. We have about 500 connections to SQL Server. Do you think that is enough memory? Why are we still having timeouts?

Five months ago we migrated our SQL server databases from 7 to 2000. Since then we have experienced timeouts very often. Sometimes we've have detected that MS Access blocks the Server, and when we kill the process everything starts to work properly. Our server has 3 GB of RAM. We have about 500 connections to SQL server. Do you think that is enough memory? Why are we still having timeouts?
If you have MS Access blocking the server, that is likely to be part of the problem. More memory is always a good thing but I've certainly seen a number of systems with 3G RAM that are dealing happily with 500 users. I'd suggest looking at what is being blocked (sp_lock is a good start here). I'd also suggest checking the transaction isolation levels in use in the application.
This was first published in November 2006

Dig deeper on Microsoft SQL Server Performance Monitoring and Tuning

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close