Standby MultiPlatform Licenses


1. Introduction


Dbvisit Standby MulitPlatform 11.0.x uses a different License key than earlier versions.

A version 6, 7, 8,9 or 10 license keys  will not be accepted by the Dbvisit Standby version 11 software.

Dbvisit Standby MultiPlatform uses a new license Module.

If you upgrade from a previous version, a new valid license key will be required.

The license key is in the format of seven blocks of 5 characters: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

A license key will look like this (this is an example demo key): 4jo70-qwp4l-7gplh-g1ekg-j3mkc-0kewl-fzl5c

A trial key is required even when installing the Dbvisit Standby MultiPlatform for evaluation. This key will be provided as part of the registration process for the download.  

The license keys are different for Oracle, and SQL Server and the same key cannot be used for both the products. The license key also depends on the OS used. The supported platforms for Standby are Linux and Windows.

The license keys generated for Oracle are tied to the db_name and the OS used like the earlier versions.

The license keys for SQL Server are Instance-based with a limit of a number of user databases per license.

If you are a support paying customer, you can contact Dbvisit Software Limited at and request your new Dbvisit Standby MultiPlatform License key which will be provided free of charge

2. Oracle Licensing

Unlike the earlier version, with Dbvisit Multiplatform the license can be only applied directly from the central console. The license key must be entered when creating a configuration. This key can either be a temporary trial key or the permanent key.

After the key is entered the status and expiration of the key can be found on the top right corner after we select the configuration.

This license key can be updated by clicking the UPDATE option ( 1 ) and entering the new license key ( 2 ).

3. Microsoft SQLServer Licensing

The license key must be applied when creating a configuration for SQLServer and the license can be applied only from the central console. The same license key can be applied to a different database configuration but for the same instance pair. In the below example the primary SQLServer Instance is on the server toru and the Instance name is SQLEXPRESS and for standby the server name is wha and the instance name is SQLEXPRESS. Any number of databases with the same instance pair can be applied with the same license key.

The license status and expiration dates can be found by clicking the configuration and on the Actions Pane top right corner.

A new license key can be updated by clicking the update option ( 1 ) and entering the new license key ( 2 )

4. PostgreSQL Licensing

The license should be applied when creating a PostgreSQL configuration. Each configuration will have different license keys.

The license expiration date can be found when selecting the configuration. The date is displayed on the right top corner of the Actions Menu.

The new key can be applied by clicking the update button.

Have more questions? Submit a request