You would like to move the MessageStats database to a different SQL server.
Note: The required database rights for the MessageStats Admin group have been simplified and all of the roles mentioned in the video are no longer required. If preferred you can assign just the db_owner and MessageStats_Admin role to the group.
In the steps described below OldServer is the server where the MessageStats database is currently installed on and NewServer is the machine on which the database will be moved to.
1. On OldServer perform a backup of the MessageStats database. To perform this use either the preferred backup software able to backup SQL databases or the backup utility of SQL Server Management Studio
2. Copy the MessageStats database backup (.bak) file to the NewServer
3. On NewServer perform a database restore (restoring from the backup generated in step 1)
Required database permissions for MessageStats to function:
Security Groups are needed to assign rights to the database. Either Local or Global Groups can be used. They should be named MessageStats Admin and MessageStats Web. If the MessageStats database resides on a SQL cluster the Groups will have to be created in Active Directory.
1. Add the MessageStats service account to the local Administrators group on NewServer
2. On NewServer (or in Active Directory if SQL is clustered) Create two groups one called MessageStats Admin (for accounts performing a gathering and administering the MessageStats console) and another called MessageStats Web (for accounts running reports)
3. Make sure the MessageStats service account is added to the MessageStats Admin group
4. the ‘Everyone’ group is typically added to the MessageStats Web group
To assign the MessageStats Admin group to the MessageStats database:
1.Launch SQL Management Studio and expand Security | Logins
2.Right click on Logins and choose New Login.
3.Click on search and find the MessageStats Admin group. Click OK.
4.Select Windows Authentication.
5.For ‘Default Database’ choose MessageStats from the drop down.
6.In the left hand column click on User Mapping.
7.For the “Users Mapped to this Login” section put a check mark in the box beside the MessageStats database.
8.Under the “Database role Memberships for” section select – Public, MessageStats_Admin and db_owner. Click OK.
To assign the MessageStats Web group to the MessageStats database:
1.Launch SQL Management Studio and expand Security | Logins
2.Right click on Logins and choose New Login.
3.Click on search and find the MessageStats Web group. Click OK.
4.Select Windows Authentication.
5.For ‘Default Database’ choose MessageStats from the drop down.
6.In the left hand column click on User Mapping.
7.For the “Users Mapped to this Login” section put a check mark in the box beside the MessageStats database.
8.Under the “Database role Memberships for” section select – Public, and MessageStats_web. Click OK
Change the MessageStats Console to use the new SQL server:
1. On the MessageStats Console server, launch the MessageStats Console
2. Drill down to the Console name. Right-click on it | Properties | Database tab
3. Next to the fleld named Locate the database on the following SQL server click on the eclipse (...) button and point to NewServer. Test connection (if required KB 3553 - https://support.quest.com/messagestats/kb/3553 - may need to be re-applied). Click OK. Click OK again
4. In the MessageStats Console ensure that connectivity to the new server has been correctly established. Go to Database Management, review the value in the bottom right corner of the Console. It should display the location of the newly moved database
Note: The Web Reports file that contains the location of the database will need to be updated as well. This file is found in: "C:\Program Files(x86)\Quest\MessageStats\QMSReports.udl". On the connection tab, update your SQL location and click OK.
Note: You may run into an error with the Default Gathering or Reporting Aggregation "User does not have permission to perform this action;; SQL Statement = EXEC PR_UpdateStatistics". If you see this error please see this KB article for resolution:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center