How can we improve PI Developer Technologies for you?

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.

7 votes
Sign in
Signed in as (Sign out)

We’ll send you updates on this idea

TimCarmichael shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
PLANNED  ·  Ray Verhoeff responded  · 

We have a new SQL query processing engine under construction. We call it the Real-Time Query Processing Engine, or RTQP Engine. We are targeting improved performance and scalability but we are also improving some of the table designs to make common queries a bit easier. We have talked to many customers about their use cases. It turns out that direct access to PI Data Archive tags is still very important. We also found several hybrid use cases such a summarizing values from a PI tag over the period of an Event Frame, and Kenneth Barber’s excellent example of aligning AF Attributes with PI Point attributes. So, we will be adding direct access to PI tags and data but not in the first release.

5 comments

Sign in
Signed in as (Sign out)
Submitting...
  • Kenneth Barber commented  ·   ·  Flag as inappropriate

    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?

  • Kenneth Barber commented  ·   ·  Flag as inappropriate

    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.

  • TimCarmichael commented  ·   ·  Flag as inappropriate

    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.

  • TimCarmichael commented  ·   ·  Flag as inappropriate

    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.

  • Vincent Kaufmann commented  ·   ·  Flag as inappropriate

    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.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED