The following summary outlines line how to move the Enterprise Reporter Database from one SQL Server® to another SQL Server®.
The following procedures assume that you have the following permissions:
• |
SQL permissions to access SQL Server® Management Studio on both the current and new SQL Server® to backup and restore the SQL database |
3 |
Start SQL Management Studio and connect to the SQL Server® where the dbReporter database resides. |
5 |
Right-click on the dbReporter database and select Tasks | Back up. |
3 |
Right-click on the database’s node and select Restore Database. |
4 |
Under Source, select Device, click the ellipsis (…). |
5 |
Click Add and browse to the backup copies. |
6 |
7 |
Under Backup sets to restore, select Restore beside the backup name. |
8 |
From the Restore database window, click OK to restore the database. |
3 |
On the Enterprise Reporter server, select All Programs | Database Wizard. |
4 |
5 |
Browse to (or type in the name of) the new SQL Server® and make sure the Enterprise Reporter database name is correct (for example, dbReporter), and click Next. |
7 |
Click OK on the Database Maintenance Wizard popup that appears regarding replication. |
8 |
Click Finish to initiate the database configuration. |
9 |
Click OK upon completion. |
1 |
Open Configuration Manager System | Information and confirm the database location. |
One SQL Server® database is created and used by Enterprise Reporter and should be included with the regular SQL Server® backup. This Discovery Management database has a default name of dbReporter.
6 |
Click Select/Upgrade Existing Database in the Database Wizard to allow Enterprise Reporter to make all of the necessary connections to the database and click Next. |
NOTE: If SQL Server® is installed on the same recovery computer as Enterprise Reporter, review the popup message about upgrading Enterprise Reporter. Select “I understand and wish to continue”. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center