How to manually migrate to MessageStats v6.0 database, on both clustered and non-clustered SQL 2000 Servers.
IMPORTANT NOTES:
- Please confirm a successful back-up of the original MessageStats Database exists before proceeding.
- These steps are known to work successfully; however, they have not been officially tested by Quest Software Quality Control.
- If any of these instructions are changed, this solution becomes unsupported by Quest Support and Development. For customization of the Quest MessageStats Product, please contact our Professional Services Organization: http://wm.quest.com/services/services.asp.
To migrate the MessageStats v6.0 database manually:
1. Unzip the attached SQL Script from this solution to the local SQL Server where the MessageStats Database resides.
2. Launch SQL Enterprise Manager.
3. Select the MessageStats Database.
4. Launch SQL Query Analyzer by selecting the Tools Menu | SQL Query Analyzer, then select File | Open.
5. Open the SQL Script that was downloaded from this solution, then select Query | Execute.
6. After the script has completed, please check the General Message bar on the bottom to verify that the "Query batch completed." message is displayed. This message indicates that the SQL script was successfully executed.
7. Right-click the T_Configuration Table under the MessageStats Database and select Open Table | Return all rows.
8. Change the values for the following columns, then close the Table:
Version = 6.0.0
Build = 6.0.0.289
Active = 1
9. Go to the Security\Logins folder in SQL Enterprise Manager.
10. Confirm that the MessageStats Admin login has the following for database access: public, ddladmin and MessageStats_Admin.
11. Confirm that the MessageStats Web login has the following for database access: public and MessageStats_Web.
12. Close SQL Enterprise Manager.
13. Confirm that the MessageStats v6.0 Console will connect by launching and confirming all settings.
