Chat now with support
Chat with Support

MessageStats 7.8.1 - Upgrade Guide

1b. Manually Upgrading the MessageStats Database on a Separate Server

In some situations, you might need to manually upgrade the MessageStats database using a script instead of using the MessageStats installer.

To migrate the MessageStats database manually, you use a SQL script called MessageStatsMigration.sql that is located in the MessageStats installation directory in a folder named SQL.

To manually migrate the MessageStats database
1
Copy the MessageStatsMigration.sql file to the SQL server on which the MessageStats database resides.
2
Open SQL Server Management Studio.
3
Connect to the SQL Server that is hosting the MessageStats Database.
Server Type = Database Engine
Server Name = SQL Server Name
Authentication = Windows Authentication or SQL Server Authentication
SQL Authentication is recommended for installations in which the reports and database are on separate servers.
4
Expand SQL Server Name and expand Databases.
5
Right-click the MessageStats database and select New Query.
6
On the Query window, select File | Open | File.
7
Locate the MessageStatsMigration.sql script file and open it.
8
Provide either the Windows Authentication or SQL Server Authentication and click Connect.
9
Select the Query Menu and Execute. Select the MessageStats Database.
This migrates the tables and roles as required.
10
Go to the Security\Logins folder in SQL Management Studio.
11
Confirm that the MessageStats Admin login has the following roles for database access:
•
public
•
db_ddladmin
•
db_securityadmin
•
MessageStats_Admin
12
Confirm that the MessageStats Web login has the following roles for database access:
•
public
•
MessageStats_Web
13
Close SQL Management Studio.
14
Upgrade the MessageStats reports and server (scheduler service). For details, see 2. Upgrading the MessageStats Reports and the MessageStats Server .
15
Confirm that the MessageStats console can connect by opening and confirming all settings.

2. Upgrading the MessageStats Reports and the MessageStats Server

2. Upgrading the MessageStats Reports
and the MessageStats Server

Next you must upgrade the MessageStats reports and the MessageStats server (console, scheduler service, and task processors) using the MessageStats installer.

It is recommended that you log on with the MessageStats service account to perform the upgrade.

To upgrade MessageStats Reports and MessageStats server
1
Copy the zipped file that contains the MessageStats release to the server that hosts the MessageStats reports and the MessageStats server.
2
Extract the contents of the compressed file to a directory on the server.
3
In the extracted MessageStats directory, double-click the setup.exe file.
4
Click Install.
A dialog appears indicating that an earlier version of MessageStats exists in this computer.
5
Click Continue.
6
Click Next, accept the license agreement and click Next.
7
Select Custom.
The installer automatically detects that the MessageStats server and the MessageStats reports components are installed. A red x is displayed beside the MessageStats Database node in the Select Features dialog, indicating that the database is not present.
a
If you manually updated the MessageStats database using a script, set the MessageStats Database to Entire feature will be unavailable.
8
Click Next.
9
Verify the server locations for the installed MessageStats database, reports, and scheduler service.
The current server is displayed by default for all the component locations.
10
Enter the SQL Server on which the MessageStats database is installed. Enter the SQL instance name after the SQL server name (SQLServer/InstanceName).
You must explicitly specify the SQL instance if
•
you are not using the default SQL instance
•
you have more than one SQL instance
•
you are using SQL Express (MyServer/SQLEXPRESS)
11
Click Next.
12
Ensure that the Share the Application Log folder option is selected and click Next.
13
Select the web site option that reflects your MessageStats reports installation and click Next.
14
Verify the SMTP server and SMTP from address settings for your report subscriptions and click Next.
15
Enter the MessageStats service account name (in domain\username format) and password.
16
Click Install.
Once the reports and MessageStats server components are installed, you are prompted to perform task migration.
 
* 
IMPORTANT: Do not run task migration if database installation was not successful.
Task migration can take a while to run. If you cancel task migration during the installation process, you can run it separately at a later time. For information about running task migration manually, see About task migration .
17
Click Next to run the Migrate.exe tool which migrates your existing tasks.
18
Click Finish.

Moving the MessageStats Database

Moving the MessageStats Database
•
Process to Move an Existing MessageStats Database
•
Backing Up the MessageStats Database
•
Restoring the MessageStats Database on the Destination Server
•
Setting Security on the New SQL Server
•
Detaching the Database
•
Moving the Database Files and Reattaching the Database
•
Updating Connections to the New Server
•
Upgrading MessageStats After the Database is Moved

Process to Move an Existing MessageStats Database

Process to Move an Existing MessageStats Database

The process of moving the MessageStats database to a different SQL server consists of the following steps:

1
Backing Up the MessageStats Database.
2
Restoring the MessageStats Database on the Destination Server.
3
Setting Security on the New SQL Server
4
Detaching the Database.
5
Moving the Database Files and Reattaching the Database.
6
Moving the Database Files and Reattaching the DatabaseUpdating Connections to the New Server.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating