For the SQL portion of SCCM... I know if you buy the SCCM server license with SQL Server Technology that it can only be used for SCCM. If you buy a full blown copy of SQL server 2005 or 2008 can it be used as a stand-alone and run other apps too? Also,do you just need a SQL Server license for SCCM...you don't need a SQL CAL in addition to each SCCM Client ML? I didn't see any mention of this but want to confirm. Thanks!

Yes, you may use the SQL server (Full blown version)for other applications. We have a our SQL server running SCCM as well as other small apps. As long as you do it in accordance with the licensing purchased with your SQL. You don't need a SQL CAL for each client. That is why you have the SCCM client CAL so you don't need to worry about that. Now if you have 5,000 clients you might not want to put anything else on the SQL server. Every enviroment is different so be carefullwith your Database loads. http://www.microsoft.com/systemcenter/configurationmanager/en/us/pricing-licensing.aspx

Hi, I feel the above answer may be somewhat misleading. If you purchase SCCM With SQL Server, in that case a SQL CAL is NOT required as per the below information taken from page 86 of the Product Use Rights (a). If the version of SQL is a standalone, then the SQL Licensing terms would apply, which are noted in part (b). a) License terms for SQL Server 2005 Technology and SQL Server 2008 Technology . If your edition of the software includes either SQL Server 2005 Technology or SQL Server 2008 Technology (e.g., System Center Configuration Manager 2007 R2 with SQL Server 2005 Technology, System Center Data Protection Manager 2010, System Center Essentials 2010 with SQL Server 2008 Technology, System Center Operations Manager 2007 R2 with SQL Server 2008 Technology and System Center Service Manager 2010 with SQL Server 2008 Technology), you may run, at any one time, one instance of that technology in one physical or virtual operating system environment on one server solely to support that software. You do not need SQL Server CALs for that use. You may create and store any number of instances of SQL Server Technology on any of your servers or storage media solely to exercise your right to run an instance of that technology under any of your software licenses as described here. You also may run one passive fail-over instance in a separate operating system environment for temporary support. You may run that instance on a server other than the licensed server. b) Multiplexing: Use of Middleware, Transaction Servers, and Multitiered architectures Sometimes organizations develop network scenarios that use various forms of hardware and/or software that reduce the number of devices or users that directly access or use the software on a particular server, often called multiplexing or pooling hardware or software. Use of such multiplexing or pooling hardware and/or software does not reduce the number of CALs required to access or use SQL Server software. A CAL is required for each distinct device or user that is connected to the multiplexing or pooling software or hardware front end. Figure 1. Multiplexing. Users / devices that access a SQL server indirectly require a CAL This is true no matter how many tiers of hardware or software exist between the SQL Server and the client devices that ultimately use its data, services or functionality. An exception to this includes the manual transfer of data from employee to employee. For example, if an employee sends an Excel version of a report to another employee, the receiving employee does not require a CAL (as long as the report does not access a SQL Server in some way). An additional exception is communication exclusively between SQL servers. Source: http://download.microsoft.com/download/1/e/6/1e68f92c-f334-4517-b610-e4dee946ef91/2008%20SQL%20Licensing%20overview%20final.docx