My SEPM DB is on SQL 2005. One of our DBA's asked if they could upgrade it to the latest, 2012 I believe.

Is there any harm in just simply upgrading the SQL version or could this possibly corrupt the SEP DB instance?

System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1

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

It's not compatible with SEPM 12.1

Make copy of db first and then upgrade it

Also make sure to back up the db on Sepm and server private key folder for your referrence

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

see solution marked in link below might help.

https://www-secure.symantec.com/connect/forums/migrating-sepm-db-sql-server-2005-2008-do-i-really-have-reinstall-sepm#comment-4618801

I don't believe SQL 2012 is out yet so if you have gotten some sort of pre-release copy it is not supported.

2008 R2 SQL is currently supported.

Hi Brian,

Do not upgrade that MS SQL server yet!  This forthcoming MS SQL 2012 release is not yet supported. (Thumbs up to the forum members who have written that, above!)

You may wish to support this Connect Forum Idea (enhancement request):

https://www-secure.symantec.com/connect/ideas/symanetc-endpoint-protection-manager-add-support-ms-sql-server-2012

In the meantime, you can upgrade from MS SQL 2005 to the 2008 version (if done properly), and definitely ensure that all clients and servers have the latest SP of whatever version MS SQL you are running.

All the best,

Mick

Looking for comments on this:

We needed to get rid of our physical 2005 SQL server (running SQL 2005 on Server 2003) it was 6 years old, out of support and failing. Our new SQL server is running SQL 2008 on Server 2008R2 as a virtual server.

I logged in to the 2 SEPM virtual servers, stopped the SEPM service on both.

• We detatched the database from the SQL 2005 server,
• copied everything database related over to the 2008 server,
• we then "attached" the SEPM database to SQL 2008,
• recreated the SQL user so the SEPM could connect,
• I then restarted the SEPM service on both servers,
• I ran the server configuration wizard for SEPM on the SEPM servers, putting in the new server name and SQL instance.
• They chugged along and connected in just a few seconds.

It's running now for 2 days - no "apparent" issues.

That's how we moved the database from SQL 2005 running on Server 2003 over to SQL2008 running on Server 2008R2.

"Thumbs up" for sharing the details of your experience, ShadowsPapa!

Here are a couple of official Symantec articles which may be of interest to this thread's followers:

How to upgrade a Microsoft SQL 2005 Server to a Newer Service Pack with Symantec Endpoint Protection Manager Connected
Article: TECH148714 | Created: 2011-01-21 | Updated: 2011-10-31 |
Article URL http://www.symantec.com/docs/TECH148714

How to reconfigure Symantec Endpoint Protection Manager to communicate with upgraded SQL Server database
Article: TECH162881 | Created: 2011-06-21 | Updated: 2011-06-30 |
Article URL http://www.symantec.com/docs/TECH162881

Hope this helps! 
 
 

Please check the following article to move your SQL database from an existing SQL Server database to a new SQL Server database.

Best Practices guide to moving the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database

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