Windows authentication removes user management from the dba. By providing
access and permission to Windows domain groups, there is no need for the dba
to take any action in when users come or leave.

If you are using SQL 2000, recognize that SQL authentication is somewhat
weak. There are no password controls (size, age, rotation, etc.) And unless
the application provides opportunities for the user to change their
password, then whoever adds the user to the server will know their login.
It's a weak system

With SQL 2005, the SQL login system is more robust. But again, if your
situation allows, Windows authentication is preferred.

--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


[quoted text, click to view]

Is there any need for SQL standard Logins, other then for non-MS systems
like Unix to be able to connect?? Shouldn't all users (who are all using
WINXP systems) be able to do what they need to through Windows Auth?

Please help me out here I just want to be sure, and hear any other ideas,
I'm sure there's something out there that I am not thinking about

Thank you.

On Fri, 21 Jul 2006 10:15:16 -0500, "WANNABE" <breichenbach <AT> istate
[quoted text, click to view]

Hi Wannabe,

Two reasons I can think of:

1. Your windows userid is member of the local administrators group; when
using SQL Server, you prefer not to run with administrator priviledges
to minimize the chance of data loss if you make a mistake. So you use a
SQL Server login with limited priviledges instead of Windows
authorization.

2. You are testing an application and need to check if the proper
authorizations have been assigned to the various roles. Instead of
loggint out and back in using various test windows logins, you can use
SQL Server logins that have been made member of the apppropriate groups.

--