如何从 AspenTech IP21 Historian 查询数据？
旧主题与新工具相结合：从 AspenTech IP21 (InfoPlus.21) 数据历史库查询 Web 应用程序数据的最佳/合适方法是什么？
过去，我通过 Aspen SqlPlus ODBC 驱动程序使用了一些非常糟糕的查询，但这似乎不是正确的方法，因为它似乎根本没有安装在 Win 7 上。
这里有人有这方面的经验吗？
Old subject, combined with new tools: What would be the best/appropriate way to query data for a web application from an AspenTech IP21 (InfoPlus.21) data historian?
In the past, I've used some pretty awful queries via the Aspen SqlPlus ODBC driver, but that doesn't seem like the right approach, as it doesn't seem to install on Win 7 at all.
Anyone here have experience with that?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
1) 确保您拥有合适版本的 Aspen 工具，更高版本的工具（7.1、7.2）将在 Windows 7 上运行，不会出现任何问题
2) 我使用 Aspen IP21 已超过 15 年，与其他工具相比，从未出现过 SQL 性能问题Oracle 或 SQL 服务器等数据库，只要 IP21 位于适当的服务器上，并且根据数据库的结构适当地编写查询。针对时间戳进行连接将会产生缓慢的查询。根据您想要完成的任务，还有多种其他方式来获取数据，通过 HISTORY 伪表、AGGREGATES 表或特定于 IP21 的其他查询技术。
3) ODBC 仍然是最标准、最简单、对我来说从任何客户端、ASP、.Net、网页、其他数据库、VB 程序、Excel VBA 等从 Ip21 获取数据的最佳性能。只是可能需要一些优化调整可能是 SQL 的编写方式。
1) make sure you have appropriate version of Aspen tools, later ones (7.1, 7.2) will run on Windows 7 with no problems
2) I have worked with Aspen IP21 going over 15 years and have never had issues with SQL performance compared to other databases like Oracle or SQL server as long as the IP21 is on an approriate server and the query is written appropriately per the structure of the database. Doing a join against timestamp is going to produce a slow query. Depending on what you want to accomplish, there are multiple other ways to get data, through HISTORY pseudo table, AGGREGATES table, or other query techniques that are specific to IP21.
3) ODBC is still the most standard, easiest, and to me best performance for getting data from Ip21 form any client, ASP, .Net, web page, other databases, VB programs, Excel VBA, etc. Just may need some optimization tweaking probably in how SQL is written.
我在 C#/ASP.NET 中使用普通 SQLPlus 驱动程序拥有丰富的经验，并且性能从来都不是问题。虽然 ODBC 驱动程序可以工作，但我遇到了某些限制，例如并不总是返回 SELECT 结果。
至于如何检查“超出规格”：
如果这是针对实时值而不是时间范围，我建议使用记录引用来简单地选择当前值。这样整个查询就保留在内存中。
对于时间范围，您必须选择范围并迭代它们，这成本更高。
I've had extensive experience using the normal SQLPlus drivers in C#/ASP.NET and performance has never been an issue. While the ODBC drivers work, I have encountered certain limitations, such as not always returning SELECTs results.
As for how to check 'out of spec':
If this is for real-time values and not for ranges of time, I would suggest using record references to simply select the current value. That way the entire query stays in memory.
For time ranges you will have to select the ranges and iterate over them, which is more costly.