Systems Management Server 2003 - SQL Licensing & Authentication Requirements
Posted on 2007-03-30
Greetings world -
A colleague of mine recently setup an SMS 2003 environment in VMWare and was having issues launching the SMS Service Manager and seeing collections data and so forth (just hourglasses). I decided to help him and blew away all the Virtual Machines and started over.
When I did so, I made only two changes to the configuration. I set the authentication mode of SQL to Windows instead of Mixed Mode, and I set the SQL Server 2000 licensing to "Per Seat" rather than "Per Processor".
Everything works now! My question is, does SMS 2003 have a technical restriction that requires Per Seat licensing on SQL 2000 rather than Per Processor? Or was it my change to the authentication mode that made it work. Or both?
Any information anyone has on their experiences with SMS 2003 and SQL 2000 would be appreciated. I'm wondering if the licensing made a big difference or not.