I would like to store the SQL table lookup attribute data into PI point for history reference, how would I can do this.
Please let me know, waiting for your reply.
If you only have a few attributes with a table lookup data reference that you would like to store the table value in a PI Point you could use Asset Analytics. Asset Analytics isn't designed to be an interface, and there are some potential pitfalls to this solutions. For example, you may not be able to get the scheduling to work correctly depending on the data pattern in the table, if the table is large this isn't a good idea for performance reasons as the analysis service caches the table in memory, and there are a few other shortcomings of this approach.
A better solution would be to use the PI Interface for Relational Database (RDBMS via ODBC). This solution is great in terms of performance, can be deployed at scale and avoid unnecessary overhead in AF. The interface writes directly to PI Points. You can create an attribute with a PI Point data reference instead of a table lookup. You can find the product information here: https://techsupport.osisoft.com/Products/PI-Interfaces-and-PI-Connectors/PI-Interface-for-Relational-Database-(RDBMS-via-ODBC)/Interface-Details
Finally, depending on your use case, if the table contains a time column, you could configure the table lookup data reference to use the time context of the table instead of outputting the value to a PI Point. There are some shortcoming to this approach as well, but this may meet your needs.
To be clear, the better solution to get data from a relational database into PI Points is to use the PI Interface for Relational Database.
Hope this helps,
I have few attribute parameters to store into pi point, So I will go with AF analytics.
will check this solution and revert on same.
Thank you Sebastien.
Retrieving data ...