The SPI agents should not be manually set. Most of the PI agent status properties are hidden. The properties that are visible are intended for support cases only. Any manual change on those settings will only be partial configuration and the agent will produce errors.
- The SQL PI should be enabled from the agent wizard and administration screens ONLY.
- If the SQL PI was not enabled for an agent, no SQL PI data is being collected (even if the ASP is set to True). The data that the user sees is from the regular existing collections that are being kept in the topologies.
- As opposed to the StealthCollect and Performance Analysis, the SQL PI does not have two repositories: short term (MW) and long term (repository), instead it has only one SQL PI repository based on Infobright database.
- Once the SQL PI is enabled for an agent, the SQL PI repository will be installed (only for the first agent). There is no option to enable SQL PI without SQL PI repository.
- Any data that is being collected by the SQL PI collections is being kept in the SQL PI repository.
Storage Requirements on PI Enabled Agents
• SQL PI Repository used disk space size is 1GB on the average and up to 2GB per Database agent.
Additional Info:
At 50 PI agents, the PI Repository should grow to ~ 100GB (over 2 years) assuming 50 PI Enabled agents and no additional are removed/added. The SQL Server and Oracle agent metrics will also grow in the FMS Repository, up to 1-2GB per agent maximum.