To determine the values, the DataReference on your EventFrame attribute is resolved. That must be able to get the data needed. If e.g. you use a PI Point DataReference, the PI data must be there when the EventFrame is retrieved in your application.
You can 'capture' values of EventFrame attributes.
Just extend your WHERE clause, like you currently have StarTime < 't'
You can store views in OLEBD EnterPrise, but you cannot define parameters on those. When calling the view from your application, you have to supply a where clause to provide further filtering.
Not a DeltaV geek...
PS: you mentioned PIOLEDB, but EventFrames are in the PI OLEDB EnterPrise provider. Minor but important difference.
I am very relieved to hear that the Event Frames Attribute Values are
stored in SQL and not in the PI archive. That makes so much more sense to
Regarding Item 2) I Tried something like
Start Time >= Date and (End Time <= Another Date or EndTime is null) and I
got start dates that were before the stated start date and end times after
the stated end date. I suspect there is some form of overlapping dates
going on here, but I couldn’t find a good description of how it works, so I
can tailor my queries the way I want them. Can you provide something like
Regarding Item 3) I saw that support for views is provided, but the current
documentation (2012) says they are stored in the module database, which I
know is in the process of being deprecated. Presumably this type of
functionality will be provided in future releases? Also, I am assuming
that these views are similar in behavior to the ones that are provided with
SQL server, namely they are pre compiled and are more performant than
normal injected SQL. Can you confirm this?
Thomas W. McCarthy | Integration Manager
*Neo PLM * | 555 Long Wharf Drive | New Haven | CT | 06511 | USA
*T1 203 292 1835 x112 | M1 203 923 3579 *
From: Roger Palmen
Sent: Friday, November 20, 2015 3:46 AM
To: Tom McCarthy <email@example.com>
Subject: Re: - PI OLEDB Event Frames Questions
PI OLEDB Event Frames Questions
reply from Roger Palmen
in PI Developers Club - View the full discussion
image001.png 5.1 KB
1) My apologies, in my first reply (since edited) i mixed up two sentences, so that showed up in your email probably. Attribute values are NOT stored in AF / SQL by default.
2) The query you describe looks good to me. Maybe sharing a list of EventFrames and the actual query will help to find the issue.
3) the current version of PI OLEDB Enterprise stores the view definitions in the AF "Configuration" database, not the Module database anymore. As the relational model is already an abstraction of the actual AFSDK calls, a precompile of queries like in SQLserver is not that relevant. The target schema is constant after all, where in SQL you need to run your query against the meta / master DB to know where to get your data.