We are currently running SEPM 11 RU5 on a Windows 2008 64 bit server. The database is a SQL 2005 on a separate server. I want to mirgate the database to our new SQL 2008 database server. I have done a search have not found a KB article or posting that describes the process. Is there a KB article that I have missed? I am guessing that the process would be similar to:

1. Remove the SEPM from any and all replication partners.
2. Backup the SEPM database.
3. Stop the Symantec Endpoint service.
3. Install the SQL 2008 client and utilities on the SEPM server.
4. Move the database to the SQL 2008 server.
5. Run the Management Server Configuration Wizard.

I am sure there are several steps I left out but it should be similar.

Here is the document which best explains the migration procedure.

 

Migrating SEPM DB to SQL 2008

https://www-secure.symantec.com/connect/blogs/migrating-sepm-db-sql-2008


with MU5 you should be good to go with this migration

https://www-secure.symantec.com/connect/forums/migration-sql
 

Seems to me in that first blog document, there's steps that are not necessary at all - I don't see a reason to reinstall anything, since it's already using SQL.
The blog assume the SEM built-in database moving to SQL2008 the way I read it.
I think Richard is pretty close in his own assumptions.......... at least that's my take on it.
I don't see a reinstall reason.......

I called Technical Support and Frank found a KB document that explains how to migrate the database to SQL 2008. It seems that you do need to uninstall SEPM. Symantec's explanation is that are some registry keys that are created when you install SEPM.

Moving an existing Symantec Endpoint Protection Manager 11 RU5 database to SQL Server 2008
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009092823041448?Open&seg=ent

I haven't finished reading the KB yet. So far it look fairly thorough.

Wow, they really made THAT painful!
Unreal - simply moving to a different SQL forces an uninstall and totally from scratch reinstall........... interesting.
THAT should be in a config file, not the registry...... IMO.