It's bad design that leveraging singleton design pattern in db connection

转载于 2012-09-03 14:31:00 发布 · 118 阅读

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/webglcn/archive/2012/09/03/2668767.html

本文探讨了使用单例模式获取数据库连接时所遇到的问题，包括无法同时开启多个SqlDataReader/SqlCommand及由此导致的线程阻塞问题。文章还强调了连接池在处理昂贵的连接开销方面的重要性，并指出创建SqlConnection实例或打开连接并不会带来显著的性能损失。

Refer to http://stackoverflow.com/questions/814206/getting-db-connection-through-singleton-class

You won't be able to open multiple SqlDataReaders/Commands with the connection at the same time and will run into thread blocking issues if you are trying to share the same connection object with multiple threads.

If you are attempting to avoid a performance hit of "new SqlConnection()" or "connection.Open()" be advised that there really is no performance hit there because of the connection pooling going on behind the scenes. Connection Pooling handles the opening/closing of the expensive connections. Not the SqlConnection object.

转载于:https://www.cnblogs.com/webglcn/archive/2012/09/03/2668767.html