Re: SQL Server Mode
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Fri, 14 Dec 2007 22:49:05 +0000 (UTC)
George Schneider (georgedschneider@xxxxxxxxxxxxxxx) writes:
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?
Particularly in SQL 2000, SQL authentication had no protection against
brute-force attacks, and the password was not very secured on the wire.
Provided that you run SQL 2005 on Win 2003, SQL accounts are now subject
the same policies as Windows accounts, so failed login attempts will
lead to lock-out etc.
Windows authentication means that users just connect with out providing
any credentials themselves; the fact that they are already logged into
Windows is sufficient.
But as mentioned elsewhere in the thread, Window authentication is not
always possible. It reqiures all accounts to be in the same domain,
or at least in a trusted domain. If all you have is a workgroup, you
can use Windows authentication, but then users needs to have the same
user/password on all machines. For a workgroup, I would definitely
recommend SQL authentication.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Re: SQL Server Mode
- From: Andrew J. Kelly
- Re: SQL Server Mode
- Prev by Date: Re: Viewing object owner in SQL 2005 - ownership chaining
- Next by Date: Re: Login failed for user . The user is not associated with a tru
- Previous by thread: Re: SQL Server Mode
- Next by thread: Re: SQL Server Mode
- Index(es):
Relevant Pages
|