지금 지원 담당자와 채팅
지원 담당자와 채팅

MessageStats 7.8 - Upgrade Guide

About SQL Security Permissions for Upgrading the Database

Generally, it is recommended that you upgrade MessageStats using the MessageStats service account. In most cases, if the account used to upgrade the MessageStats database is the database owner, you can upgrade the database without any issues.

However, for environments in which security is locked down in the SQL deployment, use the following information to determine which SQL security role assignments are required by the account used to upgrade the database:

 
Table 1. Determining the required SQL security roles.

Is the account the database owner?

Required SQL security role assignments

Yes
•
dbcreator
•
public
•
securityadmin

The account must be a member of MessageStats Admin local user group.

No
•
dbcreator
•
public
•
securityadmin
•
sysadmin

The account must be a member of MessageStats Admin local user group.

Upgrading a Complete (Single Server) MessageStats Installation

The simplest type of upgrade is for a complete installation where all the MessageStats components are installed on a single computer.

Prerequisite

Before you start the upgrade process, ensure that you are logged onto the MessageStats server with the MessageStats service account.

Download and Extract MessageStats
1
Download the latest version of MessageStats from the Support web site.
2
Extract the contents of the compressed file to a directory on your existing MessageStats server.
3
In the extracted MessageStats directory, double-click the autorun.exe file.
Verify the Upgrade Options
4
Select the Install tab, click the MessageStats link, and run the installer.
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 Complete.
8
Verify the server locations for the installed components:
•
the MessageStats database SQL server
•
the MessageStats reports IIS server
•
the server on which the MessageStats scheduler service is installed.
9
Click Next.
10
Ensure that the Share the Application Log folder option is selected and click Next.
11
Select the web site option that reflects your MessageStats reports installation and click Next.
12
Verify the SMTP server and SMTP from address settings for your report subscriptions and click Next.
13
Enter the MessageStats service account name (in domain\username format) and password.
14
Click Install.
The MessageStats Database Setup Wizard is displayed.
Migrate the Database
15
Click Next.
16
Verify the SQL server name and MessageStats database name. Ensure that the Migrate previous build check box is selected.
A summary of the selected database options are displayed.
17
Click Start.
The Installation Results screen shows whether database migration was successful.
18
Verify that the database was successfully migrated and click Done.
If a database upgrade and migration is not successful, MessageStats automatically reverts to the previous version of the database. The MessageStats database and the MessageStats product must be the same version to work properly.
Migrate Existing Tasks
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.
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 .
19
Click Next.
20
After the tasks have been migrated, click Finish.

Upgrading a Distributed Installation with a Separate Database Server

When you upgrade a distributed MessageStats installation in which the components are installed on different computers, you must upgrade the components in the following order:

1
MessageStats database
2
MessageStats reports
3
MessageStats server (includes the MessageStats scheduler service)

In the following sample procedures, the MessageStats database is installed on one server. The MessageStats reports and the MessageStats server (scheduler service, task processors, and console) are installed together on a second server.

In most installations, you use the MessageStats installer to perform the upgrades. The process consists of the following procedures:

1a. Upgrading the MessageStats Database on a Separate Server
2. Upgrading the MessageStats Reports and the MessageStats Server

However in some situations, you might have to manually upgrade the database but still use the installer to upgrade the reports and server (scheduler service). The process consists of the following procedures:

1b. Manually Upgrading the MessageStats Database on a Separate Server
2. Upgrading the MessageStats Reports and the MessageStats Server
 
* 
IMPORTANT: The database must have the same MessageStats version and build number as the MessageStats Server you are using.

1a. Upgrading the MessageStats Database on aSeparate Server

1a. Upgrading the MessageStats Database on a
Separate Server

First you must upgrade the MessageStats database by running the MessageStats installer. It is recommended that you log on with the MessageStats service account to perform the upgrade.

To upgrade the MessageStats Database
1
Download the latest version of MessageStats from the Support web site.
2
Extract the contents of the compressed file to a directory on your existing MessageStats database server.
3
In the extracted MessageStats directory, double-click the autorun.exe file.
4
Select the Install button under Quest MessageStats.
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 the database component that is installed. A red x is displayed beside the MessageStats Server and Reports nodes in the Select Features dialog, indicating that they are not present and will not be upgraded.
8
Click Next.
The server on which the MessageStats database is installed is displayed.
9
Verify the server location for the installed MessageStats database server. 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)
10
Click Next.
11
Verify that the displayed account is the MessageStats service account and click Install.
The MessageStats Database Setup Wizard Welcome page is displayed.
12
Click Next.
The existing SQL Server and MessageStats database information is displayed.
13
Ensure that the Migrate Previous Build check box is selected and click Next.
14
Verify the summary of selected options and click Start.
15
When the database migration is completed, verify that the installation results show that the database creation and migration was successful.
If a database upgrade and migration is not successful, MessageStats automatically reverts to the previous version of the database. The MessageStats database and the MessageStats product must be the same version to work properly.
16
Click Done and click Finish.
17
Upgrade the MessageStats reports and server (scheduler service). For details, see 2. Upgrading the MessageStats Reports and the MessageStats Server .
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택