This video is 1st part of Installing SEPM with Microsoft SQL Server, which has the following content
00:09:53
Adding a few useful cross-references...
Microsoft SQL Server requirements for Symantec Endpoint Security 11.0 and Symantec Network Access Control 11.0 Article URL http://www.symantec.com/docs/TECH102704 System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1 Article URL http://www.symantec.com/docs/TECH163806 A newer video: Symantec Endpoint Protection Manager 12.1 Fresh Install - SQL Database https://www-secure.symantec.com/connect/videos/symantec-endpoint-protection-manager-121-fresh-install-sql-database
Microsoft SQL Server requirements for Symantec Endpoint Security 11.0 and Symantec Network Access Control 11.0 Article URL http://www.symantec.com/docs/TECH102704
System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1 Article URL http://www.symantec.com/docs/TECH163806
A newer video:
Symantec Endpoint Protection Manager 12.1 Fresh Install - SQL Database https://www-secure.symantec.com/connect/videos/symantec-endpoint-protection-manager-121-fresh-install-sql-database
Yes, post part 2 soon!!!
Should we hope for part 2? The crowd is roaring...
I couldn't find it so wondering if the location changed for the posting.
Is it possible to export the data from your current SEPM native DB so that it can be imported into the new SQL DB or would we be starting over with new configurations and so forth? We have been running the SEPM native DB for at least 3 years and would like to keep all information and sttings for SEPM if possible, especially since the current dbsrv9.exe service is using over 200 MB of memory at times.
Thank you for posting this.
maybe Mudit, you could put it in the title?
Nice and thorough. One additional benefit is saving of memory; I'm seeing about 100MB consumed by the default (Sybase?) database server process.