SQL Server 2008: should I be using Windows auth or SQL Server auth?

Question

I have an MS-Access 2007 front end. I will have multiple users on it. They are all going to be on the network company domain. Should I be using Windows authentication or SQL Server authentication to be connecting to SQL Server 2008 via ODBC?

Answer 1

Windows auth will allow a more seamless authentication process, single sign on!

From the below article:

Disadvantages of SQL Server Authentication

• If a user is a Windows domain user who has a login and password for Windows, he must still provide another (SQL Server) login and password to connect. Keeping track of multiple names and passwords is difficult for many users. Having to provide SQL Server credentials every time that one connects to the database can be annoying.
• SQL Server Authentication cannot use Kerberos security protocol.
• Windows offers additional password policies that are not available for SQL Server logins.

Advantages of SQL Server Authentication

• Allows SQL Server to support older applications and applications provided by third parties that require SQL Server Authentication.
• Allows SQL Server to support environments with mixed operating systems, where all users are not authenticated by a Windows domain.
• Allows users to connect from unknown or untrusted domains. For instance, an application where established customers connect with assigned SQL Server logins to receive the status of their orders.
• Allows SQL Server to support Web-based applications where users create their own identities.
• Allows software developers to distribute their applications by using a complex permission hierarchy based on known, preset SQL Server logins.

Here is a good article on the pro's/con's for each. http://technet.microsoft.com/en-us/library/ms144284.aspx