大家好，
最近，我們有一位客戶告訴我們，由於安全問題，他們寧願不使用ODBC驅動程序將OsiSoft PI連接到JMP。 其他連接選項是Web API和OLEDB。 我只是想知道是否有人遇到過PI數據庫以及他們的客戶正在使用什麼來進行連接。 ODBC是否仍然是標準，還是有趨勢朝著其他方向發展？
哈德利
有多種方法可以連接到Osi PI。 經常使用ODBC，但我相信這種趨勢將會消失（將來至少會使用REST或OLE DB），一些人也通過JMP JSL的“運行程序”（例如Python）來使用它。 但是後者需要更多
需要考慮的其他事項（這是我們在2018年獲得的支持案例，因此自從現在以來OSI PI可能會有更新和更改：
The query in JMP (3rd party) takes more than 10 minutes (for 720000 events) to deliver the data, if I execute the same query in PI SQL Commander it also takes a long time to get the result displayed but not so long as in JMP. If I execute the statement a second time in the Commander it is much more faster than the first call. Why? Caching?
Yes - the ODBC takes longer than OLEDB queries, this is expected.
This is becasue the chain in the architecture and ecery point takes some time: PI ODBC -> SQL DAS -> PI OLEDB -> PI Data Archive
PI SQL Commander can be understood as PI OLEDB Enterprise. While 3rd party SAS JMP as PI ODBC.
Yes caching is also taking place. This is also correct. PI OLEDB or PI ODBC does not have its own cache with query results, but the pi data archive has read cache
2)
The query delivers around 720000 events. What is the normal rate events/sec using PI ODBC?
720 000 events depend on the location of pi data archive. Running the command locally is faster, remotly it takes more time. Also the archived data and the way of stored data in pi data archvie is important (how is the data stored internally within the archives - out-of-order, records, how many archives are covering the period (3 months), etc.)
On of the important remark: the issue is that this kind of queries (IN condition) are executed in a sequential way, in else the interpolation is made for one tag first, subsequently for the second, third and so on..
testing results:
so far.....??? need to quantify (testing)
Are there some possibilities to get some information what the ‘bottleneck’ is or is PI ODBC the wrong tool to get data for so much PI points for this long time range?
bottleneck -> PI DataArchive read cache (disk read performance)
因此，最重要的是如何建立數據庫以及在何處建立數據庫。 請不要共享實際數字或該線程（因為可能不再是當前線程），但是您可能希望提取一些發現，以至少為客戶提供一些“在哪裡看”的提示。
注意：請確保他們使用了哪種OSI PI軟件包，它們提供了一些區別，例如PI OLEDB Enterprise允許通過OLEDB連接從PI Data Archive中訪問Asset Framework元素/屬性，Pi事件框架和時間序列數據。 目前沒有典型的PI（afaik）
