Additional notes for SQL PI when migrating SQL Server or Oracle agents between Agent Managers (FglAM) (4226918)

How to move DB agent associated to SQL PI repository A to SQL PI repository B?

How to Re-Assign a DB agent to a different Oracle or SQL Server SQL SPI Repository

How to reassign DB agents to a different SQL PI Repository

You may need to re-assign a supported DB agent to a different Oracle or SQL Server SQL (SPI) Repository for load balancing or general organizational purposes.

A migration utility for SQL Server and Oracle agents has been included beginning with the 5.7.1.1 database cartridges. The migration tool allows you to perform resource balancing between the agent managers running Oracle agents with and without the SQL PI extension installed.

The SQL PI Repository stores data associated with SQL Performance dashboard when enabled on a database agent. This data is referenced and displayed in the FMS Web Console and database agent dashboards. 

The SQL PI functionality has the following constraints:

1. All DB agents from the same agent manager must be connected to the same SQL PI repository. 
2. Only one SQL PI Repository can currently be deployed on a installed FglAM instance.

When a new or existing DB agent is marked to be SQL PI enabled the following logic is used:

1. The DB Agent Installer searches for any other DB agent that runs on the same agent manager and is already SQL PI enabled.
2. That SPI Repository is selected by default if any are pre-existing on that FglAM.
3. If no SPI repository exists, the Foglight  administrator can select a different Agent Manager with or without SQL PI deployed.

Once an agent is migrated to the new FglAM, the new migrated agent will keep submitting data to the existing topologies so no data will be lost.