Best Practice guide for moving Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database
Article ID: 151506
How can I move the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database?
In order to move the Symantec Endpoint Protection Manager SQL Database (DB), please follow the steps as outlined below:
- Detach the Database in question from the Existing Database in SQL 2000 via the "SQL 2000 Enterprise Manager."
Note: If using SQL 2005, the "SQL Server Management Studio".
- After the Database is detached, navigate to the appropriate data folder where the existing SQL server data files are stored.
C:\Program Files\Microsoft SQL Server\MSSQL\xxxx\DATA
C:\Program Files\Microsoft SQL Server\MSSQL\DATA.
- Copy the following database files to the data folder for the new server housing the new SQL DB
- <db_name.NDF >
- <db_name.LDF >
- On the server where you want to move the existing SQL DB to, Right click on the Database instance, and click on Tasks>All Tasks> Attach Database.
- Type the path to the < db_name .MDF > file, and the wizard will automatically pick up the other files. (. NDF and . LDF )
- Click OK. The wizard would automatically collate and attach the Symantec Endpoint Protection Manager console database to the new SQL Database.
- Once complete, Run the "Management Server Configuration Wizard" and point the Symantec Endpoint Protection Manager to the new server housing the newly attached Database.
- In the Database Server name tab, type in the <HostName> /<ComputerName> of the new server, fill in the remaining required details and complete the configuration wizard.
- Once the wizard has completed its task, log into the Symantec Endpoint Protection Manager Console and the configured Policies and Clients will appear as in the previous installation.