Re: connection options to yukon

I am leaning towards Windows Authentication too. But what about a domain
account vs local account? Any pros & cons of one over the other?

thanks!

"Sahil Malik [MVP]" <contactmethrumyblog@xxxxxxxxxx> wrote in message
news:e1lakyraFHA.2736@xxxxxxxxxxxxxxxxxxxxxxx
> Connection pooling does not depend on what method you choose to connect -
> Windows auth or Sql auth.
> Connection pooling depends on the fact that repeated SqlConnection objects
> use the exact same connection string.
>
> My recommendation would be to use Windows authentication over sql Auth
> because it is more secure. It is more secure because there is no password
> to
> manage :) (or it is managed by the OS).
>
> Please let me know if you have any additional questions.
>
> - Sahil Malik [MVP]
> http://codebetter.com/blogs/sahil.malik/
> My upcoming ADO.NET 2.0 book - http://tinyurl.com/9bync
>
>
>
>
> <param@xxxxxxxxxxxxxxxx> wrote in message
> news:urNVrlkaFHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi all, i am a newbie to SQL2005. I have had experience developing apps
>> on
>> .net 1.1 and sql 2000. I am currently working on developing a new
>> solution
>> and looking into feasibility of using sql 2005 as the database and .net
> 1.1
>> as the front end with the enterprise library jan 2005 block to connect to
>> the database. I may also decide to use asp.net 2.0 depending on the new
>> features available which I am still exploring. The question I had is what
> is
>> the best way for an asp.net application (1.1 or 2.0) to connect to a sql
>> 2005 database and make best use of connection pooling.
>>
>> 1. SQL Server Authentication
>>
>> PROS
>>
>> 1. No need for windows accounts or cals
>> 2. Performance
>>
>> CONS
>>
>> 1. Asp.net app needs to store username & password somewhere.
>>
>>
>> 2. Domain Level Windows Account
>>
>> PROS
>>
>> 1. No need for application to store password
>> 2. Easy Management in a Server Farm & DB Connectivity
>>
>> CONS
>>
>> 1. Performance
>>
>> 3. Local Level Windows Account
>>
>> PROS
>>
>> 1. No need for application to store password
>> 2. Performance
>>
>> CONS
>>
>> 1. Complicated management in a server farm and need to create account on
>> each machine with same name etc.
>>
>> 4. SQL 2005 Application Roles?
>>
>>
>> Can anyone make some best practice recommendations?
>>
>> Much appreciated!
>>
>>
>>
>
>


.

Relevant Pages

  • Re: I want to be convinced; convince me.
    ... > write down both pros and cons, but you'll see that most are cons, as I ... > content windows that are not at the left border of the screen. ... > love the Mac" is just too much to let slide. ...
    (comp.sys.mac.advocacy)
  • Re: MP3-Player in Python?
    ... > I am currently trying to code a little MP3-Player in Python. ... > Cons: I was not able to get the length in seconds etc. ... > Pros: Lots of functionality. ... I tried this under windows, ...
    (comp.lang.python)
  • Re: Pros and cons for WIndows XP
    ... accoridng to the assignment just the pros and cons of windows xp ... the credit for you i hope would be helping out a fellow computer person. ... Pros and cons of Windows XP ...
    (microsoft.public.windowsxp.basics)
  • Re: Winforms or Webforms
    ... > own organisation(or the one which you give rights) to connect otherwise it ... Pros of using Windows forms ... Cons of using windows forms ...
    (microsoft.public.dotnet.languages.vb)
  • Any experience with InduSind Bank
    ... Does anyone have any experience with InduSind bank? ... pros and cons of having an account with them. ...
    (soc.culture.indian)