Skip to main content

RCS with SQL databases

The Visual KPI Remote Context Server can connect to any SQL data source. All that is required is ODBC access with appropriate read-level permissions. This page guides you on what you need to know and do to use RCS with your SQL database.

dashboard22
Training

Refer to Visual KPI training to learn all about Visual KPI RCS.

SQL RCS Best Practices​

For all interfaced fields, Visual KPI supports the recommended interface name or interface ID if used with the correct field name.

Example​

If you have an interface named ODBC-Localhost with:

  • ID = 4e432114-499c-44e1-994d-7690de272b74

You can either:

  1. Use Latitude as the lookup value and set LatitudeInterface to ODBC-Localhost.
  2. Use Latitude and LatitudeInterfaceID where Latitude is the lookup value and LatitudeInterfaceID is 4e432114-499c-44e1-994d-7690de272b74.

Mapping​

For effective mapping between foreign systems and Visual KPI, it is crucial to assign a unique and consistent identifier to each object in the system such as KPI, Group, Trend, etc. This identifier can be in the form of a string, GUID or an integer, and it should be specific to the object type. By doing so, Visual KPI can ensure that there is no confusion in the mapping process.

Note

If the ID changes in the foreign system, a new object will be created in Visual KPI and the old object will be deleted.

Every definition query (KPI, Group, Chart) must include a column called METAID with a unique value.

For your reference, please see the links to the reference tables below:

Tutorial​

Refer to the SQL Tutorial page for a full guide and demo on how to install and use the SQL Remote Context Server.

Feedback