Endpoint Protection

Hi,

We have 2 different environments with a SEPM in each environment. Both of them has got their own SQL Server which replicates with each other. They want to change the second environment to either SEPM and SQL on the same Server or embedded database on the one environment.

Does anyone know where I can find a best practice on why to use SQL and why on a seperate Server and not on the SEPM Server.

Thanks

How many clients you have? Embedded will handle up to 5,000 clients. If you have more than SQL is the way to go.

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

https://www-secure.symantec.com/connect/forums/embedded-database-or-sql-database

https://www-secure.symantec.com/connect/forums/embedded-database-vs-sequel-server

We have 16000 on the one doamin and 150 on the other, but it is replicating. I need a best practice from Symantec why SQL on a separate Server is the better way to go.

For that many clients, SQL is needed.

Because of the resources being used, no way could the box host both SEPM and SQL.

Here is the guide:

Symantec Endpoint Protection (SEP) Sizing and Scalability recommendations

https://www-secure.symantec.com/connect/forums/best-practices-sql-server-0

About choosing a database type

http://www.symantec.com/business/support/index?page=content&id=HOWTO55329

Symantec™ Endpoint Protection 12.1.2 Sizing and

Scalability Best Practices

Attachment(s)

SizingSizabilityBestPractices_SEP12.1_0.pdf   910 KB 1 version

Hi,

Thank you for posting in Symantec community.

Embedded database supports upto 5000 clients per SEPM . SQL Database supports 80,000 clients per SEPM.

Refer this article: About choosing a database type

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

SQL database can be on same machine or at remote machine.

It gives better redundancy if SEPM and SQL's are on two different machines.