Endpoint Protection

If I will be using MS SQL database for my SEPM, given that I have 2000 clients reporting to SEPM will MS SQL will have 2000 client licenses also??

Thanks,

Hi Gilbert,

SQL will be holding the data of 2000 clients. However if you can elaborate the query, I would be in better position to answer the query.

Regards,
Nirav Mistry.

 Use the embedded Db, it suppots up to 5000 nodes.

For SQL licensing, get per-processor.  

What i mean is, 2000 sep clients are reporting on sepm with sql db, do we need 2000 licenses of sql as well?

In general, there are three options for licensing SQL Server in a production environment:

Hi Gilbert,

You dont need 2000 SQL licenses, only one license for SQL server 2005 is needed because the licensing of SQL server depends on the number of client accessing the database. In case of symantec endpoint protection manager there would be only one client (which is symantec endpoint protection manager) accessing it.

The clients will communicate through symantec endpoint protection manager and endpoint manager will process the request and will add the data to the database. 

In case of failover and load balancing there would be two symantec endpiont manager, in that case you will require two licenses of SQL server 2005. 

The above provided information is colated using below mentioned link as reference.

http://www.microsoft.com/sqlserver/2005/en/us/licensing.aspx

Regards,
Nirav Mistry.

Assuming you'll only be using it for one database, use the Processor License. Some clients use their existing SQL Server and just add an instance for SEP.

Thanks to all your  clear and concise information.SQL licensing is now clear to me.

Could you please confirm that this does not come into play.  (My assumption is that clients do not use the database, the database is about the clients.)

Multiplexing: Using Middleware, Transaction Servers, and Multitiered Architecture

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 client access licenses (CALs) required to access or use SQL Server software. A CAL is required for each distinct device or user to the multiplexing or pooling software or hardware front end. This remains true no matter how many tiers of hardware or software exist between the server running 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 a Microsoft Excel version of a report to another employee, the receiving employee does not require a CAL. An additional exception is communication exclusively between the servers running SQL Server.