opensubscriber
   Find in this group all groups
 
Unknown more information…

d : dotnet-web@discuss.develop.com 21 June 2008 • 9:09PM -0400

Re: [DOTNET-WEB] sql server authentication with named domain account
by Mark Aurit

REPLY TO AUTHOR
 
REPLY TO GROUP



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 <markaurit@gmai...> 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
>



--

=======================
MarkAurit@gmai...

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

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

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.