SQL Connection Pool timeout setting and SQL Server remote query setting

Question

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

Steven · Accepted Answer · 2011-04-18 08:37:50Z

1

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.

answered Apr 18, 2011 at 8:37

Steven

174k26 gold badges355 silver badges453 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Thomas Over a year ago

when connection time out happen? if front end UI trying to connect sql server for long time then connection time out happen? or for a long time any connection open from UI but not close & staying idle then also connection time out happen? please guide.

Collectives™ on Stack Overflow

SQL Connection Pool timeout setting and SQL Server remote query setting

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related