Chat now with support
Chat with Support

MessageStats 7.8.1 - Upgrade Guide

Backing Up the MessageStats Database

The first step is the back up your MessageStats database on the existing SQL server.

To back up the MessageStats database
1
Start SQL Server Management Studio on the source computer.
2
Expand the Databases node.
3
Right-click the MessageStats database and select Tasks | Backup Database.
4
Under the Destination section of the Backup Database window, click Add.
5
Enter a name for the MessageStats database backup file (such as MessageStatsDb.bak) in the File Name field.
6
Ensure the Overwrite Media option is set.
This option is located in the Overwrite section of the Backup Database window.
7
Click OK from the Backup Database window.

Restoring the MessageStats Databaseon the Destination Server

Restoring the MessageStats Database
on the Destination Server

Next, you must restore the MessageStats database on the new SQL server.

To restore the MessageStats database
1
Start SQL Server Management Studio on the destination SQL server.
2
Right-click the Databases node and select Tasks | Restore Database.
3
Enter MessageStats in the [Restore as database:] field on the Restore Database window.
4
Under the Restore section of the Backup Database window, select the [From device] option.
5
Click Select Devices.
6
Click Add and select the backup file that you created.
7
Click OK until the Restore Database window is displayed.
8
Click OK on the Restore Database window to restore the database.

Setting Security on the New SQL Server

Security groups are needed to assign rights to the MessageStats database on the new SQL server. You must create two groups, either local groups or global groups, named MessageStats Admin and MessageStats Web.

If the MessageStats database resides on a SQL cluster, create the groups in Active Directory.

To create the MessageStats groups
1
Add the MessageStats service account to the local Administrators group on the new SQL server.
2
Create two groups called MessageStats Admin and MessageStats Web.
•
The MessageStats Admin group is used for accounts that perform a gathering and administer the MessageStats console.
•
The MessageStats Web group is used for accounts that render the reports.
3
Add the MessageStats service account to the MessageStats Admin group.
4
Add Everyone to the MessageStats Web group.
To assign the MessageStats Admin group to the MessageStats database
1
Open SQL Server Management Studio and expand Security | Logins.
2
Right-click Logins and select New Login.
3
Click Search and find the MessageStats Admin group. Click OK.
4
Select Windows Authentication.
If the database and reports are on separate servers, SQL authentication is recommended. See If SQL Authentication is Used .
However, if Windows Authentication is required, you must set up Kerberos delegation from the MessageStats Reports server to the MessageStats Database server. For more information, see the section titled “Deploying a Distributed Installation Using Windows Authentication” in the MessageStats Deployment Guide.
5
For the Default Database, select MessageStats from the drop-down list.
6
In the left hand column, click User Mapping.
7
In the Users Mapped to this Login section, select check box beside the MessageStats database.
8
Under Database role memberships for, select the following roles for membership:
•
Public
•
MessageStats_Admin
•
db_securityadmin
•
db_ddladmin
9
Click OK.
To assign the MessageStats Web group to the MessageStats database
1
Open SQL Server Management Studio and expand Security | Logins.
2
Right-click Logins and select New Login.
3
Click Search and find the MessageStats Web group. Click OK.
4
Select Windows Authentication.
If the database and reports are on separate servers, SQL authentication is recommended. See If SQL Authentication is Used .
However, if Windows Authentication is required, you must set up Kerberos delegation from the MessageStats Reports server to the MessageStats Database server. For more information, see the section titled “Deploying a Distributed Installation Using Windows Authentication” in the MessageStats Deployment Guide.
5
For the Default Database, select MessageStats from the drop-down list.
6
In the left column, click User Mapping.
7
In the Users Mapped to this Login section, select check box beside the MessageStats database.
8
Under Database role memberships for, select the following roles for membership:
•
Public
•
MessageStats_Web.
9
Click OK.
If SQL Authentication is Used

If SQL authentication is being used, you must create a SQL account on the new SQL server and assign the appropriate database roles.

Assign the following database roles to the new SQL account:

•
Public
•
Messagestats_Web

Detaching the Database

You must also detach the database, in preparation for moving the database files to the new location.

To detach the database and move database files
1
Back up your data.
2
Open SQL Server Management Studio.
3
Right-click the Databases folder, select MessageStats and select Properties.
4
Select the Files tab.
5
Note the MessageStats data file and log file names. Scroll right to see the full file names, normally MessageStats.mdf and MessageStats.ldf.
6
Click Cancel to close the window.
7
Right-click the MessageStats database and select Tasks | Detach Database.
8
Click Clear if there are connections using this database.
9
Click OK.
The following prompt is displayed “Do you want to notify the currently connected users that their sessions in the database will be ended?”
10
Click Yes.
The STATUS in the Detach Database dialog box should say “The database is ready to detach”.
11
Click OK.
The following prompt is displayed “Detaching database has completed successfully”.
12
Click OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating