reducing sql connections & connection pools
What is the philosophy with connection pools in do factory? It seems we make a connection on every query. Is there a way to use connection pools? Or is that a bad idea?
Is this addressed in the SQL Database Pattern Framework?
Alan Anderson, Jan 28, 2016
Thanks for the answers guys. This helps me think this through a bit. From my understanding, connection pooling is happening in ADO.NET and since do factory is using ADO.Net, then it just magically happens for me. Does that sound right?
Again, thanks for the answers.
Alan Anderson, Feb 19, 2016
If i understand correctly your questions you can do something like this:
Create a list where you can store the connectios you have already created
Then when you want to "create" a connection you can check the list (your pool) to see if there is already an existing connection and take it from there so you don't have to create a new one.
If the connection does not exist add it to the list and that's how you can have you pool of connections and not create a new one each time you want to query the database.
I Hope it helps. Regards
Ramon Aguilar, Feb 18, 2016
I didn't understand your question - "What is the philosophy with connection pools in do factory"
Mukta Madankar, Jan 29, 2016
Connection pooling is handled by the database drivers themselves.
You can configure this (on the connectionstring), but generally you should not have to change this..
Hope this helps.
Jack Poorte, Jan 29, 2016