Is it necessary or advantageous to write custom connection pooling code when developing applications in .NET with an SQL Server database? I know that ADO.NET gives you the option to enable/disable connection pooling -- does that mean that it's built into the framework and I don't need to worry about it? Why do people talk about writing their own connection pooling software and how is this different than what's built into ADO.NET?Is it necessary or advantageous to write custom
阅读背景：
.NET/SQL服务器中的连接池?
来源：互联网
分享到：
