Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Is SQL Server Enterprise always a system requirement for installing Symantec Critical System Protection?

Created: 06 Feb 2013 • Updated: 11 Feb 2013 | 1 comment
This issue has been solved. See solution.

Background for my question:

Currently I do not use Symantec Critical System Protection. I notice that the published system requirements for Symantec Critical System Protection specifies SQL Server Enterprise. Currently, I use a hardware Symantec Endpoint Protection Manager (SEPM).  In the near future I plan to replace it with a Virtual SEPM.  After I have the Virtual SEPM in place, I plan to expand that SEPM's management ability to manage Symantec endpoints that are not in my WAN.  That means setting up a public IP Address for that SEPM so that the 'out of WAN' clients can be managed by the SEPM. My total SEP client count is about 550.  I want to install SCSP on that Virtual SEPM to harden it, considering it will be a public facing server. That will be the only use of SCSP in my environment.  Now, the question...


When installing SCSP in the scenario above is SQL Server Enterprise still a requirement?  I ask because I will have no SCSP endpoints to manage, nor will I have any other servers managed by SCSP. So, I do not see that will have a need for the robustness of the Enterprise version of SQL.  SQL Server Enterprise is rather expensive.  Is there another alternative besides SQL Server Enterprise?

Comments 1 CommentJump to latest comment

Alex_CST's picture

No, a single standalone SCSP will be fine with the embedded install of SQL 2005 Express - use that and you're golden.

Please mark posts as solutions if they solve your problem!