connection options to yukon

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: via group membership
    ... were given access to the database. ... a Windows account and haven't granted that account access to ... even though they don't have a login set up on the server. ...
    (microsoft.public.sqlserver.security)
  • Re: ADO recordset problem
    ... The folder the database is sitting in does not have write permissions to the ... In classic ASP, that windows account was IUSR_machinename???. ... > application to update database. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Associating a Windows account with a user
    ... Actually what I have is a database with three users but only one of them is associated with a Windows account. ... Juan Dent, M.Sc. "Narayana Vyas Kondreddi" wrote:> Is this the case of an orphanned user, due to moving the db from one domain> to another or something? ... > Can you simply grant access to that Windows login to SQL Server using ...
    (microsoft.public.sqlserver.security)
  • Removed login as user from db but it still has access
    ... I have a windows account that is not supposed to have access to a database so I removed it as a user in the database by un-checking the "permit" checkbox in the login properties. ... I tried to login in with the account but it could still access data in the database. ...
    (microsoft.public.sqlserver.security)