SQL连接池超时设置和SQL Server远程查询设置
ASP.Net ConnectionStrings 默认情况下启用持久池，而 SQL Server 默认情况下有 600 秒的远程查询超时。我假设对于工作中的池化来说，每个池化连接都会长时间保持打开状态。
600秒默认设置是否会影响连接池的使用？这样会时不时地出现随机连接超时错误吗？或者它与游泳池无缝配合。我应该将最大远程查询超时更改为 0（无限）吗？
谢谢
ASP.Net ConnectionStrings have persistent pooling on by default, and SQL Server default has a 600 second Remote query timeout. I assume that for a pooling at works each pooling connection would stay open for a long time.
Does the 600 second default setting affect the use of connection pooling? Such that a random connection timeout error would occur from time to time? or it works with pool seamlessly. Should I change max remote query timeout to 0 (infinite) instead?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当然，超时会影响池化。如果您有长时间运行的数据库查询，并保持打开状态 600 秒，并且新请求不断传入，则变化是连接池的连接即将耗尽。
Of course the timeout affects pooling. If you have long running database queries that stay open for 600 seconds, and new requests are comming in, changes are that the connection pool is running out of connections.