Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Declined
Categories PI OLEDB Enterprise
Created by Guest
Created on Aug 23, 2022

Allow PIOLEDB Enterprise to connect directly to a PI Data Archive

If PI OLEDB Provider is not going to be further developed, allow PI OLEDB Enterprise to connect directly to a PI Data Archive. There are times when an SQL type query is needed, but the data structure has not been mapped to an AF server yet.
  • ADMIN RESPONSE
    Aug 23, 2022
    This capability is not currently a priority. As such, I am setting the status of this idea to declined. We will update this thread if there is any change.
  • Attach files
  • Guest
    Reply
    |
    Aug 23, 2022
    What sorts of things are you looking to do that can't current;y be accomplished with the OLEDB classic provider? The classic provider is still being updated with bug fixes but no real feature enhancements but in my opinion there doesn't seem much to add to the current schema.
  • Guest
    Reply
    |
    Aug 23, 2022
    In response to Vincent Kaufmann, "What sorts of things are you looking to ..." PI OLEDB Provider can only connect to PI Data Archives, not an AF server; PI OLEDB Enterprise can only connect to an AF server, not a PI Data Archive. For the number of PI Data Archives we have, high double digits, some of the data has been added to AF, but, by and large, not all of it. When an application is written, being able to use a single access method rather than having to code for two methods reduces coding time and the installation base.   Assuming the access path is stored in a configuration area (INI file, registry, .config file), changing the file (PI Data Archive name or AF server name) completes the access change. The queries will change from tags to attributes, but that is minor compared to changing access methods.
  • Guest
    Reply
    |
    Aug 23, 2022
    In response to Vincent Kaufmann, "What sorts of things are you looking to ..." In addition, from the 'PI OLEDB Provider' overview page:   OSIsoft will continue to maintain PI OLEDB Provider but does not plan any major enhancements. For new projects, we recommended using PI OLEDB Enterprise, which provides access to PI System data through the PI Asset Framework (PI AF).   If PI OLEDB Enterprise is being suggested as the path forward, it needs to be able to do everything PI OLEDB Provider can do.
  • Kenneth Barber
    Reply
    |
    Aug 23, 2022
    Having PI OLEDB Provider as part of PI OLEDB Enterprise is important for managing the connection between the PI Data Archive and the PI Asset Framework. For example, it would be nice to write a query that returns the engineering units, point type, digital state set, and security settings from the PI Data Archive AND the UOM, value type, enumeration set, and security settings from the PI Asset Framework. This lets you see if the tags are consistent with the element attributes. You would also be able to write a query that identifies which PI tags have not been mapped to an element attribute. This would help massively with completing PI Asset Framework configuration. As a workaround, I currently use Excel to query both the PI Data Archive and the PI Asset Framework into separate tables. Then I use INDEX & MATCH to bring the information of one table into the other.
  • Kenneth Barber
    Reply
    |
    Aug 23, 2022
    I see that not even the ConfigString of attributes is available in PI SQL Client, so you currently cannot even view which PI Points are associated with which attributes, let alone query PI Point attributes. Is there a timeline for the direct access to PI Points?