There should be nothing special, IMO.
Install SQL to a server, install SEPM and point it to the server.
You do need to install SQL client to the SEPM, at least with SQL2005.
Otherwise, it's a matter of defaults, pretty much.
We've certainly done nothing special at all - frankly, because the SQL server was built to serve other much larger applications and databases.
If Symantec went around stating "You must install and configure your SQl server a certain way for SEPM to work" there'd be a huge uproar! No one can afford to customize their SQL server to fit a specific app. That apps need to comply with SQL standards, period.
In other words, SEPM should deal with any standard SQL install and need nothing special.
I don't imagine that a multi-million dollar business running gigs of databases on a corporate SQL server is going to shut down other apps to make a security application work........
So, I guess I"m confused as to why you might be thinking the SQL server has to be customized to work with SEPM (SEP Manager)
Can you be more specific please?