AF Tables Max size

I have a very large table that I need to include in our PI System. It has 5 columns and more than 100,000 rows. The idea is to use it as a lookup table for expected generation values, based on hour, irradiance, and month, for each of our parks.

What is the best way to integrate this table into the PI System?

Does anyone see an alternative solution to address this need?

  • Hi ​,

    The best way to integrate this will depend on how you want to consume the attributes linked to this table. But the general approach is to use Stored Procedures (or queries) with parameters to filter the dataset returned. The parameter values can then be configured on the Attribute configuration to only return the data you are requesting.

    Which are the 5 columns and how you plan to use the Expected Generation? Are you going to show only the latest value for one park, or for multiple parks on the same display? Or are you going to show it in a trend what would be the time range?

  • Hello,

    I understand that your intent is to link the table, not import it correct? If so, your best option in my experience is to use parameters for your linked table , as hinted by ​ .(See : Parameters for linked table queries)

    This will limit the amount of data retrieved from the external database to just what is needed on a per element/attribute basis. Suggest you give it a try and let us know how it goes