2 of 2 people found this helpful
Views published as PI Views are not meant to be consumed directly through SQL. Instead, they should be accessed via ODBC by installing the PI ODBC driver on the client machine.
The architecture section of the manual provides this explanation:
The PI ODBC driver on the client serves as the point of contact for the remote client application, requesting and receiving PI View data on behalf of the client through interaction with PI SQL DAS on the server.
Edit: When accessing PI Views using the PI ODBC driver, they are displayed as their view names, not as their GUID.
You can find instructions on how to set up and configure the PI ODBC driver here: https://livelibrary.osisoft.com/LiveLibrary/content/en/bi-v4/GUID-E3CAFD0D-FD80-4C91-9905-105738784A81
If you want your users to access the SQL tables directly, you can create a SQL target and publish the data to a different SQL database. Only PI Views should be stored in the PIIntegratorDB database.
Makes sense... Teaching training classes for the next several days, so I will have to try this later in the week.
Worked great... It only took a few of minutes to 1) download the ODBC installation, 2) install and configure the ODBC connection to see the views and 3) extract the data with a PI SQL Query...
I then retrieved the data with PowerBI...
Very cool and quote simple once I wrapped my head around how the data was flowing...