CODEWITHSUNDEEP
c#sqlvb.netconnection-pooling
IT researcher
IT researcher

Reputation: 3304

Connection pooling and Appdomain

This question is related to my old question .

1) I have a vb.net application which requires connections to some databases.So now if i open multiple instance of same application(exe files) then it uses different connection or uses multiple connection. So can i make it to use single connection?

2) I heard about Appdomain(An AppDomain provides a layer of isolation within a process) . Does it help in making the connection to be drawn from same pool and make optimal use of resources? This article has something related to it.

Upvotes: 3

Views: 957

Answers (2)

Ted Elliott
Ted Elliott

Reputation: 3503

Each AppDomain would have its own Connection Pool, so no I don't think using AppDomains would help in your case.

Upvotes: 0

Richard
Richard

Reputation: 109170

Different processes (your case #1) do not (and cannot) share database connections, each connection is unique to the process.

I do not know whether connection pools are per process or per-appdomain.1 But it is unlikely to make much difference. The model that you should be aiming for is to create, use and then close connections around each functional database operation. Do not try and keep them open, rather try and keep them closed. This maximises the re-use opportunities for re-use.

Unless you have a particular will a few excess connections over what is theoretically needed the default pooling while avoiding holding connections open will just work.

1 As connections are reset before being returned from the pool it would be rather hard to determine which of these is the case. Perhaps a test program that had one app domain open, use and close one connection before another app domain repeated the process and see if one or two connections to the database were established.

Upvotes: 2

Related Questions