C# Programming
02-10-2013, 04:11 PM
At my same company, we are using sql server 2008 r2 and C# 2010 and 2008 web, desktop and console applications that are accessing the same tables. Alot of time the tables are being accessed at the same time.
Thus my question is when do you recommend setting up connection pooling to the database. In other words, limiting the number of connections that can be setup to the database? I want to prevent too many deadlocks from occuring.
Thus can you tell me how the following:
1. when do you recommend connection pooling be setup?
2. Does it make a difference if this connection pooling is a web, desktop, console or some other C# application?
3. Can you point me to a reference and or some me some code how to setup the connection pooling?
Thus my question is when do you recommend setting up connection pooling to the database. In other words, limiting the number of connections that can be setup to the database? I want to prevent too many deadlocks from occuring.
Thus can you tell me how the following:
1. when do you recommend connection pooling be setup?
2. Does it make a difference if this connection pooling is a web, desktop, console or some other C# application?
3. Can you point me to a reference and or some me some code how to setup the connection pooling?