G. Migration Procedure and Notes on Migration
To upgrade PFM - Agent for Microsoft SQL Server, you need to perform overwrite installation on PFM - Agent for Microsoft SQL Server. For details about the installation procedure, see 2. Installation and Setup.
For details about notes on upgrading the versions of Performance Management programs, see the section describing the notes on version upgrading in the chapter and appendix that explain installation and setup in the JP1/Performance Management Planning and Configuration Guide.
This appendix shows the notes on upgrading the version of PFM - Agent for Microsoft SQL Server.
-
Do not uninstall the old version of PFM - Agent for Microsoft SQL Server during upgrading. If you uninstall it, performance data created in the old version is deleted and will no longer be available in the new version.
-
When you perform overwrite installation on a PFM - Agent for Microsoft SQL Server program, the following information is updated automatically:
-
Store database files of Agent Store service
-
ini file
-
Instance environment of PFM - Agent for Microsoft SQL Server
-
-
In Performance Management programs of version 08-00 or newer, the locations of the Store executing programs (jpcsto.exe and stpqlpr.exe) have been changed. When PFM - Manager and PFM - Agent are upgraded to version 08-00 or newer, the Store executing programs at the older locations are deleted.
-
In a logical host environment, when port numbers for Microsoft SQL Server are set to other than standard, in version 11-10 or earlier you need to specify a 32-bit alias by using SQL Server Client Network Utility on the PFM - Agent host or any other tool, but in version 11-50 or later you need to specify a 64-bit alias.
If the alias settings are incorrect, the KAVF21810-E message is output to the agent log error file and connection to Microsoft SQL Server will fail.
For details about alias settings, see 3.3.2(5) Notes when a non-default Microsoft SQL Server port number.
Note that you do not need to specify a 32-bit alias. If the 32-bit alias is not used except PFM - Agent for Microsoft SQL Server, there are no problems even if you delete it.
-
If you upgrade version 11-10 or earlier to version 11-50 or later, object permissions required to monitor Microsoft SQL Server are added. If you specify object permissions for user accounts that are used for monitoring, add object permissions shown in the following table. For details about required object permissions, see 2.1.4(2)(c) Login permissions of the Microsoft SQL Server.
Table G‒1: Object permissions added in 11-50 or later Records
Object permissions granted to users required for collecting records
If SQL Server version 2014 or earlier
If SQL Server version 2016 or later
PD_DD, PI_DI
Grant the SELECT permission for the following objects in the master database:
-
sysperfinfo
Grant the SELECT permission for the following objects in the master database:
-
sys.dm_os_performance_counters
If the permissions are not sufficient, the following message is output to the agent log error file.
-
If SQL Server version 2014 or earlier
KAVF21812-E SQL Server (ADO) returned an error.
(rc = 0x80040e09, msg = SELECT permission was denied on the object 'sysperfinfo', database 'mssqlsystemresource', schema '<the-user-account-used-for-monitoring>'.)
-
If SQL Server version 2016 or later
KAVF21812-E SQL Server (ODBC) returned an error.
(rc = 42000, msg = [Microsoft][ODBC SQL Server Driver][SQL Server]SELECT permission was denied on the object 'dm_os_performance_counters', database, 'mssqlsystemresource', schema '<the-user-account-used-for-monitoring>'.)
-