|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
timeout trouble in SQL Server 2005
applications that connect to it to MS SQL Server 2005 when we had been running InterBase 6.x. Since then queries return much faster, except there will be periods throughout the day ranging from 5-45 minutes where almost every other query will timeout. When we were running InterBase the entire system would slow down and users would complain because it took forever for them to get things done, this was the main reason we upgraded to SQL Server. I am just wondering if other people have had trouble with timeouts in SQL Server 2005 and been able to work through the issue, if so how did you do it? We have tried several things, most recently to move the tempdb to its own Raid array, but that actually seems to have made things worse and the server now uses less RAM. I must say I'm asking this somewhat out of desperation as word came down from the mount today that if the timeout issue isn't fixed within a week we'll be moving back to InterBase. I'm sure I don't have to explain what a grievous thought that is. Thanks, We have been experiencing something very similar in our test
environment that is making us nervous about putting SQL2K5 into production. Queries will execute fine until for no apparent reason they begin timing out. The execution plan yeilds no clue as they are identical and the only way of eradicating the issue is to restart sql. The timeouts occur frequently in the developer environment (WinXP sp2, SQL2K5 Developer Edition, VS2003/2005) on Winforms and ASP.NET projects. It has also occurred on 2 occasions on a test server (Win 2K3 Standard sp1, SQL 2K5 Standard) running an ASP.NET application under minimal load. Does anyone have any ideas what is causing this? Cheers, Mark. Contrap***@gmail.com wrote: Show quoteHide quote > In December my company converted our databases/server and all of the > applications that connect to it to MS SQL Server 2005 when we had been > running InterBase 6.x. Since then queries return much faster, except > there will be periods throughout the day ranging from 5-45 minutes > where almost every other query will timeout. When we were running > InterBase the entire system would slow down and users would complain > because it took forever for them to get things done, this was the main > reason we upgraded to SQL Server. > > I am just wondering if other people have had trouble with timeouts in > SQL Server 2005 and been able to work through the issue, if so how did > you do it? We have tried several things, most recently to move the > tempdb to its own Raid array, but that actually seems to have made > things worse and the server now uses less RAM. > > I must say I'm asking this somewhat out of desperation as word came > down from the mount today that if the timeout issue isn't fixed > within a week we'll be moving back to InterBase. I'm sure I > don't have to explain what a grievous thought that is. > > Thanks,  
Other interesting topics
|
|||||||||||||||||||||||
