Utilities

This section discusses the new and revised functionality to the Pervasive PSQL utilities.

Pervasive Control Center (PCC)

PCC includes the following changes:

•

Capacity Usage Viewer

•

Capacity Usage Viewer

PCC now includes functionality to monitor graphically the concurrent sessions and data usage for all database engines. This feature, called Capacity Usage Viewer, is especially useful when you are considering migrating from PSQL Server to PSQL Vx Server, because of the difference in the way those two editions are licensed.

You access the capacity usage graphs from the right-click context menu of the desired database server in Pervasive PSQL Explorer.

See Capacity Usage Viewer in Pervasive PSQL User's Guide.

PCC now integrates a Monitor utility. You access it from the right-click context menu of the desired database engine in Pervasive PSQL Explorer.

The integrated Monitor presents information in the form of a series of tabs and provides the same functionality as the GUI Monitor and CLI Monitor. In addition, the integrated Monitor allows you to display more data, select which columns of data to display, and sort the columns. You can monitor multiple engines at the same time and compare them side by side.

The GUI Monitor and CLI Monitor are still included with Pervasive PSQL. However, the GUI Monitor is deprecated and will be removed from the product in a future release. Its replacement is the Monitor integrated into PCC, which will be enhanced in future releases.

See Monitor in Pervasive PSQL User's Guide and Monitoring Database Resources in Advanced Operations Guide.

License Administrator

The following table summarizes the changes to License Administrator. See License Administration chapter in Pervasive PSQL User's Guide for details.

Table 5

License Administrator Changes

Repair functionality

The repair feature allows you to repair a product key in a “failed validation” or “disabled” state. The repair process also re-authorizes the key on the same machine. The default number of allowed repairs per key is 5.

License Administrator prompts you to acknowledge that you are performing the repair on a genuine copy of Pervasive PSQL. Your acknowledgement affirms that the license is being used in accordance with the terms and conditions of the End User License Agreement (EULA) and that the license has not been installed on more machines than the maximum allowed by the license.

Depending on the circumstances, some keys cannot be repaired. However, if the state change has resulted because of hardware configuration changes to a machine, and the machine is still in operation, repair is an appropriate solution.

On the GUI, you access this functionality with the “Repair” button or from the right-click menu for a product key.

For the CLI, you access the functionality with the “repair” option.

Apply to Authorize

Certain terminology has been revised in this release to enhance understanding. “Authorize” is the term now used to describe the action of associating a key with a machine signature to ensure that the copy of Pervasive PSQL is legitimate.

On the GUI, the “Apply” button is now labeled “Authorize.”

For the CLI, the “apply” option is now “authorize.” For backwards compatibility, the CLI still accepts the “apply” option but the option is no longer listed in the help information for the utility.

Delete to Deauthorize

Certain terminology has been revised in this release to enhance understanding. “Deauthorize” is the term now used to describe the action of disassociating a key with a machine signature.

On the GUI, the “Delete” button is now labeled “Deauthorize.”

For the CLI, the “delete” option is now “deauthorize.” For backwards compatibility, the CLI still accepts the “delete” option but that option is no longer listed in the help information for the utility.

Validate functionality

The validate functionality has been removed from the GUI to enhance understanding because validation was often confused with authorization. In addition, the repair functionality and the authorization functionality include key validation. A separate validate action is no longer required.

For backwards compatibility, the CLI License Administrator still accepts the “validate” option and the help information still lists the option.

Refresh functionality

To streamline the License Administrator GUI, the “Refresh” button has been removed. The refresh functionality available through the Windows operating system (F5 by default) refreshes the License Administrator GUI. A separate refresh feature is not required.