Very often you get folks who think that when a client connects to the SQL Server directly via a SmartClient (Windows App), then you need a CAL for each client BUT you don't need a CAL for each client if they connect to SQL via a middle tier (like a IIS). Their assumptions is because they going through a single connection from IIS to SQL and not a connection each from client to SQL, so only one license is required. Note: There is no version of SMS that runs on MSDE. SMS requires SQL Server
Since SMS 2.0 was released before the multiplexing constraints were put in place in SQL 2000, SMS 2.0 was grandfathered. So, to use SQL behind SMS 2.0, just buy SQL in per server for your primary sites and you do not require SQL CAL's.
For SMS 2003, there is a new version of the SMS 2003 Server SKU called, "SMS 2003 Server with SQL 2000 Technologies". This is explained in this doc (http://download.microsoft.com/download/a/5/f/a5fc3270-2fe6-4536-b228-6b333ab8569d/PURJuly2005.doc).
This SKU allows you to get your SMS Primary Site license, plus a license of SQL Server to run that site server on (or any primary site server or MOM DB) w/o requiring any additional SQL licenses. This is the model MS encourages all of our ISV partners that utilize SQL to use. If you do own SQL CAL's for all the devices that SMS manages, you can buy the regular SMS 2003 Server SKU. If you do not, then you should buy the SQL 2000 Technologies SKU.
/Gill
Source: Bill Anderson & Patch Management Mailing List
Posted
Aug 03 2005, 04:29 PM
by
sar