Systems Management Server 2003 - SQL Licensing & Authentication Requirements

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.
amendalaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJComputerNetworksCommented:
SQL 2000 license mode does not matter  (I use per seat)

Authentication mode does not matter.   (I use Mixed mode.)
0
amendalaAuthor Commented:
Interesting.

When I install using Per Processor licensing no SQL and Mixed mode authentication, my virtualized environment does not function properly... hmm.

However, when I reinstalled using Per Seat and Windows auth, it works fine.  I do believe you are correct that the authentication mode doesn't matter because I have a production environment SMS 2003 setup with SQL Server 2000 running using Mixed Mode auth. and it functions.  Still wondering about the licensing...

Any input from anyone else?
0
NJComputerNetworksCommented:
This table shows that both SQL licensing types are supported:  

(easier to see in the link:  http://www.microsoft.com/technet/sms/2003/evaluate/faq/default.mspx#ECF
)

Q. When does SMS 2003 require a Microsoft SQL Server™ CAL?
A. The following table describes when SMS 2003 requires SQL Server CALs.

SMS license type SQL Server license type SQL Server CAL for SMS 2003 required
Standalone
 Standalone per processor
 No
 
Standalone
 Standalone server/CAL
 Yes. An SMS 2003 server and every device managed by SMS, including desktops, laptops, servers, secondary site servers, and hand-helds, require a SQL Server CAL license.
 
SMS 2003 with SQL Server 2000 Technology
 SMS 2003 with SQL Server 2000 Technology or MOM 2000 with SQL Server 2000 Technology
 No
 
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.