如何从 asmx Web 服务管理多个 ado.net 数据库连接
由于 IIS 为每个请求分配一个工作线程,因此我打算创建新对象来服务每个请求。我有两个问题:
创建新对象来服务每个请求是否有效? (甚至还有替代方案吗?)
创建新连接并为每个请求打开和关闭它是否是线程安全、高效和最佳实践,如下所示:
using (MySqlConnection conn = new MySqlConnection(ConfigurationManager.ConnectionStrings["MySqlConnectionString"].ConnectionString)) { conn.Open(); MySqlCommand cmd = new MySqlCommand("SELECT password FROM Admin WHERE username='" + username + "'", conn); object dbp = cmd.ExecuteScalar(); conn.Close(); }
PS。这个例子取自这个网站。我用的是oracle数据库。
谢谢:马蒂
Since IIS assigns a worker thread for each request I've intention to create new object to serve each request. I have 2 questions:
Is it efficient to create new object to serve each request? (is there even alternatice?)
Is it thread safe, efficient and best practice to create new connection, and open&close it for each request like below:
using (MySqlConnection conn = new MySqlConnection(ConfigurationManager.ConnectionStrings["MySqlConnectionString"].ConnectionString)) { conn.Open(); MySqlCommand cmd = new MySqlCommand("SELECT password FROM Admin WHERE username='" + username + "'", conn); object dbp = cmd.ExecuteScalar(); conn.Close(); }
PS. this example is taken from this site. I use oracle db.
Thanks: Matti
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
当您执行
new SomeSqlConnection()
时,您实际上并不是每次都创建一个新连接。由于创建数据库连接的成本很高,ADO.NET 保留一个连接池并从那里提取连接。您还可以删除对Close
方法的调用。以下是您可以在每个请求中安全使用的代码片段:When you do
new SomeSqlConnection()
you actually don't create a new connection every time. As database connections are expensive to create ADO.NET keeps a connection pool and draws connections from there. You could also remove the call to theClose
method. Here's a snippet you can safely use in each request:正如达林在 他的回答,您应该允许连接池机制完成其工作。不要尝试构建一些“聪明”的东西,它不会那么好。
数据库连接等昂贵资源的黄金法则是晚获取、早释放。只要你遵守这一点,你就会做得很好。
As Darin correctly states in his answer, you should allow the connection pooling mechanism to do its job. Don't try and build something 'clever', it won't be as good.
The golden rule with expensive resources such as database connections is to acquire late and release early. As long as you abide by that then you'll do just fine.