Endpoint Protection

Hello all,

We are in the process of standing up a new server that is going to act as our primary SEPM server for multiple sites. Our biggest issue is if we are going to be able to stick with the free embedded database, or if we are going to have to purchase SQL. I've been searching online for the past few hours and have been able to find any recommended suggestions for SEPM as to when you should use one database or the other. We've heard varying numbers of the recommended clients for the embedded database but can't find any confirmation.

Is there any documentation for the latest version of SEPM, that outlines how many clients the embedded database is good for, as well as instructions on moving to SQL down the road? Any guide that is current / updated that outlines why we should choose one or the other.

Thanks!

Embedded DB should be able to handle up to 5,000 clients. One SQL DB should be able to do up to 80,000 clients.

Additional info here:

http://www.symantec.com/docs/HOWTO81044

If you would like to use some of SQL queries to get additional data and reports from database, then move to MS SQL, because you can not do that with embedded DB (you can, but you need to take it offline for SEPM).

For customers with more then 1000 clients, we do recommend (if they can) to use MS SQL, but embedded DB shoud handle up to 5000 clients (as Brian wrote in reply).

Hi,

I think that on this link you can find information which you require
https://support.symantec.com/en_US/article.DOC4448.html

In document named SizingSizabilityBestPractices_SEP14.pdf, among others, you can find following:

--------------------------------------------------
For the following client-to-server ratios, Symantec recommends the following databases:

• For installations with a client-to-server ratio of ≤5,000:1, using the default log settings, Symantec recommends the embedded databases
• For installations with a client-to-server ratio >5,000:1, or that require large log sizes, Symantec recommends a separate SQL Server database. For SQL Server database sizing, see the database vendor's sizing tools or guides.

--------------------------------------------------

If you use Embedded database and at one moment you want to migrate it to MS SQL you can follow guidelines from this links (they are little old, but still valid).

https://support.symantec.com/en_US/article.TECH102547.html
https://www.symantec.com/connect/articles/move-database-sepm-embedded-microsoft-sql-server

I hope this helps...

Best regards