Defualt Pooling

Defualt Pooling

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
-- 
Ammar S. Mitoori
IT Head QIMCO Co.
Tel : +9744831199
Mobile : +9745378400
Fax : +9744831643

date: Thu, 3 Jul 2008 01:51:01 -0700 author: Pure Heart

RE: Defualt Pooling

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

"Pure Heart" wrote:

> 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
> -- 
> Ammar S. Mitoori
> IT Head QIMCO Co.
> Tel : +9744831199
> Mobile : +9745378400
> Fax : +9744831643

date: Thu, 3 Jul 2008 14:43:00 -0700 author: Linchi Shea

Re: Defualt Pooling

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).

-- 
__________________________________________________________________________
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)
____________________________________________________________________________________________

"Pure Heart"  wrote in message 
news:1B670D52-5CBB-4172-94A7-F916EDDEB28E@microsoft.com...
> 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
> -- 
> Ammar S. Mitoori
> IT Head QIMCO Co.
> Tel : +9744831199
> Mobile : +9745378400
> Fax : +9744831643

date: Thu, 3 Jul 2008 15:03:23 -0700 author: William Vaughn [MVP]

Re: Defualt Pooling

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
-- 
Ammar S. Mitoori
IT Head QIMCO Co.
Tel : +9744831199
Mobile : +9745378400
Fax : +9744831643


"William Vaughn [MVP]" wrote:

> 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).
> 
> -- 
> __________________________________________________________________________
> 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)
> ____________________________________________________________________________________________
> 
> "Pure Heart"  wrote in message 
> news:1B670D52-5CBB-4172-94A7-F916EDDEB28E@microsoft.com...
> > 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
> > -- 
> > Ammar S. Mitoori
> > IT Head QIMCO Co.
> > Tel : +9744831199
> > Mobile : +9745378400
> > Fax : +9744831643 
>

date: Thu, 10 Jul 2008 03:47:01 -0700 author: Pure Heart

Re: Defualt Pooling

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.

"Pure Heart"  wrote in message 
news:F79EEC0E-7BB5-4691-8B2C-243C01F9B747@microsoft.com...
> 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
> -- 
> Ammar S. Mitoori
> IT Head QIMCO Co.
> Tel : +9744831199
> Mobile : +9745378400
> Fax : +9744831643
>
>
> "William Vaughn [MVP]" wrote:
>
>> 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).
>>
>> -- 
>> __________________________________________________________________________
>> 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)
>> ____________________________________________________________________________________________
>>
>> "Pure Heart"  wrote in message
>> news:1B670D52-5CBB-4172-94A7-F916EDDEB28E@microsoft.com...
>> > 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
>> > -- 
>> > Ammar S. Mitoori
>> > IT Head QIMCO Co.
>> > Tel : +9744831199
>> > Mobile : +9745378400
>> > Fax : +9744831643
>>

-- 
__________________________________________________________________________
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)
____________________________________________________________________________________________

date: Sun, 13 Jul 2008 16:11:48 -0700 author: William Vaughn \(MVP\)