Endpoint Protection

Installed SEP 12 client on a Win 2003 server with SQL 2000 installed and the existing databases crashed, anyone having issues with client on SQL servers?

The Symantec Endpoint Protection Manager includes an embedded database, and this is the only choice in Small Business Edition. In the Enterprise version, you may use the embedded database or one of the following versions of Microsoft SQL Server:

SQL Server 2000, SP4 or later
SQL Server 2005, SP2 or later
SQL Server 2008
SQL Server 2008 R2
check the system reqyirement

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

Check this fourms.

http://www.symantec.com/connect/forums/compatible-version-sql-sepm-121-ru1

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

Please check above

I had found this chart, but it appears to suggest SEP Manager,

My issue is client only this server is not a management server or even a GUP server, just a simple client having issues after installation.

Does anyone have just the SEP 12 client running "protecting" a server that happens to be a SQL 2000 server?

Thanks,

JayM

Hi JayM,

With default settings and policies, there should be no trouble at all with a SEP 12.1 client and MS SQL.  It should not interfere with MS SQL's processes, files, or databases.

You may wish to create manual exceptions if you have any suspicion that SEP is related to the crash. Here are a couple of articles that may be of interest.

Can Symantec AntiVirus or Symantec Endpoint Protection scan a MS SQL database?
Article URL http://www.symantec.com/docs/TECH100129 
 

How to exclude MS SQL files and folders using Centralized Exceptions
Article URL http://www.symantec.com/docs/TECH105240 
 

Final note: MS SQL 2000 is a product long retired by its manufacturer.  You may wish to upgrade to a supported version if any critical business datbases are still using MS SQL 2000.

Hope this helps!