SQL服务器超时 [英] SQL server timeout

问题描述

我的应用程序是在传统的ASP开发的，但也使用asp.net，因为我在迁移.NET中的应用程序。它使用SQL Server数据库和托管的Windows Server 2003上。

my application is developed on classic asp, but also uses asp.net as I am migrating the application on .Net. Its using SQL server as database and hosted on Windows server 2003.

现在的问题是，应用程序继续工作完全正常了很长时间，但再经过一段时间的SQL Server提供了超时错误，它能够满足任何提出的要求。它当我重新启动我的SQL服务器，甚至IIS没有得到，甚至固定的，最终我不得不重新启动每一只解决问题的时间我的服务器。

Now the problem is that the application continue to work perfectly fine for a long time but then after some time SQL server gives timeout error and it could fulfill any of the requests made. It doesn't get fixed even when I restart my SQL server or even IIS, ultimately I have to restart my server every time which only fixes the problem.

任何想法可能会导致什么问题？只给一个rought的想法，该网站在高峰时期使用了约300人。

Any idea what might be causing the problem? Just to give a rought idea, the site is used by around 300 people at peak times.

任何想法可能会导致什么问题？只给一个rought的想法，该网站在高峰时期使用了约300人。我certainely关闭连接无处不在，每一页上我的结束code关闭连接。如果最终页面之前发生错误，则厚望处理程序关闭连接。所以，我相信，关闭连接是不是一个问题。并且没有打开的连接，如果我看到了SQL日志。我们的服务器，只有一个盒子，有SQL Server，IIS，易网邮（我们的邮件服务器）。我已经重新启动SQL Server之后，它并没有解决问题。只有重新启动Windows服务器，它的工作。从perfom，IO使用率是相当高的。请问有什么建议吗？

Any idea what might be causing the problem? Just to give a rought idea, the site is used by around 300 people at peak times. I am certainely closing connection everywhere, my end code on each page closes the connection. If an error occurs before the end page, the expection handler closes the connection. So I am sure that closing the connection isn't an issue. And that there are no open connection if I see the sql logs. Our server, only one box, has SQL Server, IIS, iMail (our mail server). After I had restarted SQL Server, it did not solve the problem. Only restarting Windows Server, it worked. From perfom, IO usage is quite high. Is there any suggestions?

谢谢，

推荐答案

这听起来很像有一些你没有清理正确的非托管资源。我们没有足够的信息来确切地知道是什么资源可以，所以我们所能做的是猜测。

It sounds a lot like there's an unmanaged resource of some kind that you aren't cleaning up properly. We don't have enough information to know exactly what that resource might be, so all we can do is guess.

我的第一直觉就是数据库连接，除了重新启动的重新启动SQL Server应该修复它，如果是这样的话。其次在名单上的文件句柄和线程，因此，如果你做任何多线程的工作或额外的文件IO，这将是东西来看待。请记住，在ASP.Net中，使用语句（不是指令）是你的朋友。

My first instinct is database connections, except that restarting that restarting sql server should fix it if that were the case. Next on the list is file handles and threads, so if you do any multithreading work or extra file io that would be something to look at. Remember, in ASP.Net, the using statement (not directive) is your friend.

这篇关于SQL服务器超时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！