July 23, 2015 at 3:41 pm
Hi,
We were getting below error 10 days ago:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
We fixed it by creating separate app pool for each site, created indexes and made some code changes for closing connections. After these changes for last 10 days everything was running fine and all our sql queries were running in mili seconds.
Today, we restarted the server and within few hours of restart, we again started getting below error:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Event Viewer is showing above errors after every few minutes now. Some of the queries are now taking 10+ seconds for running which were taking just few mili seconds from last few days. I ran below query and found that NumberOfConnections value was 250+ when server was slow.
SELECT DB_NAME(dbid) as DBName, COUNT(dbid) as NumberOfConnections, loginame as LoginName
FROM sys.sysprocesses WHERE dbid > 0 GROUP BY dbid, loginame
We are using SQL Server 2008 R2 Express edition and server has 8 GB RAM. Are there any settings or updates we should make to fix this issue?
July 24, 2015 at 1:10 am
hi.first ,i think u should find out what ther server in doing when the server is slow.
1.is there waits or blocking?
2.check sql server error log. check whether any server options has been changed.
Thanks!
July 24, 2015 at 5:51 am
SQL 2008R2 Express Edition has the following limitations -
Maximum 10 GB per database.
Uses no more than 1 processor.
Uses no more than 1 GB of internal memory.
Every user connection takes up resources too therefore it could be that your SQL Server is struggling for resources. Run sp_who2 to see which processes are causing waits or having high resource utilization.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply