How can we improve the PI Server?

Store PI Data Archive information in an SQL Server database

Most of the PI Data Archive information that is accessible from PI System Management tools is perfect for a relational database: PI Identities, PI Mappings, PI Point attributes, PI Message Logs, etc.

Moving all of this to an SQL Server database would make it easier for the PI Data Archive to communicate with:
• PI Asset Framework (which already uses SQL Server),
• PI OLEDB Enterprise (currently responsible for translating SQL queries to native PI requests),
• PI Builder (translates the PI file format to a relational database format anyways), and, most importantly,
• the user (users know relational databases, but they do not currently know how the PI Data Archive stores its information, so they are stuck with PI System Management Tools and its limitations)

The use of an SQL Server database can lead to a simpler, more transparent, more flexible PI Data Archive. There would be less "translation" code for OSIsoft to maintain and the user can write queries to the PI Data Archive more easily.

2 votes
Sign in Sign in with OSIsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Kenneth Barber shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in Sign in with OSIsoft
Signed in as (Sign out)
  • Kenneth Barber commented  ·   ·  Flag as inappropriate

    I forgot to use the almighty buzzword. If users can query the PI Data Archive more easily, then that makes the PI Data Archive more EXTENSIBLE.

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