Re: SQL Server Mode

I look at it this way...

If I am only going to have users on a Windows Domain connecting to the database then logically the domain security is better than creating and then providing username and passwords to users.

If you have external applications and users outside of the Domain using your databases and you dont want to grant them rights to the domain then mixed mode is the way to go.

The good news is that in SQL Server 2005 you can change the Authentication mode after install...
http://msdn2.microsoft.com/en-us/library/ms188670.aspx


--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/


"Ben Nevarez" <BenNevarez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0D6C1C50-DA03-41E6-82A2-F575C52C99C6@xxxxxxxxxxxxxxxx

A few notes from BOL:

"Windows Authentication Mode is much more secure than Mixed Mode"

"Windows Authentication utilizes Kerberos security protocol, provides
password policy enforcement in terms of complexity validation for strong
passwords, provides support for account lockout, and supports password
expiration"

"Security Note: When possible, use Windows Authentication"

"SQL Server Authentication is provided for backward compatibility only. When
possible, use Windows Authentication"

Hope this helps,

Ben Nevarez
Senior Database Administrator
AIG SunAmerica



"George Schneider" wrote:

what do you mean it depends on what we are doing and how?

We run several db's fro everything from our fax server to our web site db
how can i determine which is best.

how is windows more secure than mixed mode?

"Andrew J. Kelly" wrote:

> Windows is generally more secure but which is better depends on what > you are
> doing and how.
>
> -- > Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "George Schneider" <georgedschneider@xxxxxxxxxxxxxxx> wrote in message
> news:D540F786-37EE-42A2-BF72-9ACDA9E01E4E@xxxxxxxxxxxxxxxx
> > IS it better to use mixed mode or windows authentication mode? Which
> > method
> > is more secure?
>
>

.

Relevant Pages

  • Re: Brute Force
    ... Security reasons: ... Windows Authentication has certain benefits over SQL Server Authentication, ...
    (microsoft.public.sqlserver.security)
  • Re: security with networklogin username?
    ... Access User Level Security has nothing at all to do with Windows ... user will not have to enter a username and password. ... but "depending on Windows authentication" is not the same thing as ...
    (microsoft.public.access.security)
  • Re: General questions about LDAP, GC and access permissions
    ... Windows Communication Foundation) they are authenticated with the regular ... this is done by examing what groups the user is a member of. ... Since the regular windows authentication is used, ... trusted domain in an external forest. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Help please to authenticate Windows users
    ... status error code as well as Win32 error code -- I know the HTTP status code ... Windows Authentication automatically works if the machines are joined to the ... Is VS.Net on the same machine as IIS ...
    (microsoft.public.inetserver.iis.security)
  • Re: Intermittent access to web site secured with Windows authentication
    ... Marcus ... > Windows Authentication is connection-based and not delegatable. ... > various elements of Internet networking that can prevent Windows ... > likely work in your access scenario. ...
    (microsoft.public.inetserver.iis.security)