Personally I would *not* use Mixed mode if I am able to - on SQL Server 2000 at least.
Integrated Windows Auth gives you better logging (to the Windows event log), plus all the password management goodness that is available in AD (password length, history, complexity, lockout etc). None of that is available with SQL Server logins. Additionally, if you go mixed mode, there's an additional set of credentials you need to start monitoring and managing. With SQL Server 2008, Microsoft's realised that mixed mode isn't going away, so some of these features are available with SQL Server logins now. But that functionality doesn't exist in SQL Server 2000. Cheers Ken From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Friday, 22 August 2008 7:13 AM To: NT System Admin Issues Subject: RE: SQL 2k Install Yea, I looked that up and saw this issue and consulted w/ Vendor regarding SQL2k EOL issue. The version of ERP we are stuck on (various) reasons is not compatible with SQL 2005. Bah... Thanks for the Auth info, jlc From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 2:56 PM To: NT System Admin Issues Subject: RE: SQL 2k Install Don't install sql 2000. Sql 2005 MINIMUM. That being said, I always used "mixed", so I can have a separate 'sa' account. Without "mixed" sa is mapped to administrator. Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 4:47 PM To: NT System Admin Issues Subject: SQL 2k Install I have to install SQL 2000 for an ERP app, what is your recommended setup parameter with respect to Authentication Mode: Windows Only, or Mixed Mode with an SA account? What's the diff? Thanks! jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
