Defualt Pooling

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Pure Heart - 03 Jul 2008 09:51 GMT

Hi

if SQL Server uses pooling even if i didnt do any setting in my connection
string i wanted to know haw this default setting will behave if i sent with
each connection string of my application a different user name and password ?
will it make a new pool for each connection ? isnt there a way to overcome
that because i depend on SQL Security in my applications, thank you

Signature

Ammar S. Mitoori
IT Head QIMCO Co.
Tel : +9744831199
Mobile : +9745378400
Fax : +9744831643

Reply to this Message

Linchi Shea - 03 Jul 2008 22:43 GMT

This is not a SQL Server issue, but an application layer issue. And I don't
believe different Windows identities can share the same connection pool.

Linchi

> Hi
>
[quoted text clipped - 3 lines]
> will it make a new pool for each connection ? isnt there a way to overcome
> that because i depend on SQL Security in my applications, thank you

Reply to this Message

William Vaughn [MVP] - 03 Jul 2008 23:03 GMT

SQL Server does NOT implement the Connection Pool. That's done in the
application/client layer. Each time the ConnectionString changes, the
client application is given a new Connection Pool. However, if the same
application is run by different users, each gets his/her own pool(s). In a
Windows Forms application, there is little need to use pooling (but that is
debatable). In ASP.NET these are essential and in this case one (generally)
does not use the user's credentials to open the connection.

I discuss the Connection Pool in many places including several whitepapers
on my blog www.betav.com\blog\billva and devote a couple dozen pages to it
in my book including a lot of examples on how to monitor the pool(s).

Signature

__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________

> Hi
>
[quoted text clipped - 5 lines]
> will it make a new pool for each connection ? isnt there a way to overcome
> that because i depend on SQL Security in my applications, thank you

Reply to this Message

Pure Heart - 10 Jul 2008 11:47 GMT

so if i open a connection and then dispose it will the pooling
ifnore the dispose and keep the connection object or what exactly ?

thank you

Signature

Ammar S. Mitoori
IT Head QIMCO Co.
Tel : +9744831199
Mobile : +9745378400
Fax : +9744831643

> SQL Server does NOT implement the Connection Pool. That's done in the
> application/client layer. Each time the ConnectionString changes, the
[quoted text clipped - 17 lines]
> > will it make a new pool for each connection ? isnt there a way to overcome
> > that because i depend on SQL Security in my applications, thank you

Reply to this Message

William Vaughn (MVP) - 14 Jul 2008 00:11 GMT

Dispose either destroys the object or marks it for disposal by the GC. It
has no affect on the which is handled by the .NET Data provider. Next time
you use the same connection, in the same process you'll get the same pool.

> so if i open a connection and then dispose it will the pooling
> ifnore the dispose and keep the connection object or what exactly ?
[quoted text clipped - 29 lines]
>> > overcome
>> > that because i depend on SQL Security in my applications, thank you

Signature

Reply to this Message