Re: sql server authentication with named domain account

Unless the "dirty little secret" of integrated security is that behind
the scenes a seperate connection string is
being created per user.  Its a whole lot easier, when creating 2 of what
appear to be different authentication
mechanisms, to merely abstract one up a level and use it to call the second.

Shawn Wildermuth wrote:
> Pooling is supposed to be per Connection String (which would suppose that
> Integrated security would not cause fragmentation).  If you want to test
> this, make sure you don't do it under the debugger as under the debugger
> pooling is disabled.  I'd use Profiler and a test app to test it.  I did
> this years ago when I wrote my book and it worked as expected, but that was
> under 1.0/1.1 not 2.0 or later.
>
> Thanks,
>
> Shawn Wildermuth
> http://adoguy.com
> http://wildermuthconsulting.com
> http://www.silverlight-tour.com
> Microsoft MVP (C#), MCSD.NET, Author and Speaker
>
> The Silverlight Tour is coming to a city near you!
>
>
> -----Original Message-----
> From: Discussion of building .NET applications targeted for the Web
> [mailto:[email protected]] On Behalf Of Mark Aurit
> Sent: Saturday, June 21, 2008 9:10 AM
> To: [email protected]
> Subject: Re: [DOTNET-WEB] sql server authentication with named domain
> account
>
> Which is what Id hoped would be the case.  But the below MSDN article, under
> "Pool Fragmentation Due to Integrated Security", would seem to say the
> opposite; that the pool is at the individual user level and therefore not
> conducive to scalibility.  In other words, the ado.net version of running
> under
> the user identity, which as you say its not a good thing.
> http://msdn.microsoft.com/en-us/library/8xx3tyca.aspx
>
> On Fri, Jun 13, 2008 at 7:01 AM, Mark Aurit <[email protected]> wrote:
>
>
>> (I posted this yesterday but it didnt come back.  Since its of important
>> to me right now Im going to post it
>> again, sorry if you are getting it twice)
>>
>> Im creating an asp.net/sql server app; Id prefer to use a sql server
>> account to maximize connection pooling, our security guy wants
>> integrated security.  We've reached an agreement where I can use a
>> single account as long as its a domain account, but Ive been unable to
>> figure out how to do so (if its even possible). Im thinking I either
>> need to use integrated security but force sql server to use a single
>> account, or use a regular connection string, naming the domain account
>> and password with Integrated Security=false.
>> Does want I want to do sound possible?
>> Thanks, Mark
>>
>> ===================================
>> This list is hosted by DevelopMentor(R)  http://www.develop.com
>>
>> View archives and manage your subscription(s) at
>> http://discuss.develop.com
>>
>>
>
>
>
> --
>
> =======================
> [email protected]
>
> ===================================
> This list is hosted by DevelopMentorR  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
>
> ===================================
> This list is hosted by DevelopMentor®  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
>
>

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com