As a PI administrator I want the integrator to detect new attributes on a template and add them to existing views automatically. This would be easier than creating a new view and asking users to reference this new output.23 votes
This feature has been considered and has been rejected as not practical. SQL Server targets and other relational databases, files, and other destinations do not support efficient means of adding columns and inserting new data into existing data structures. There is a heavy reliance on bulk calls for performance reasons.
Alternatives involve post processing a more generic table that can handle attribute additions.
During Integrator installation, we would like to choose the name of the Integrator's backend SQL database instead of using the default name PIIntegratorDB.
Some use cases include:
-Being able to use the naming scheme that our organization's DBA requires for SQL Server tables
-Installing more than one Integrator instance on the same SQL Server
Workaround: Follow the steps in KB01640 - Installing multiple Integrator instances on one SQL server.12 votes
This is an old idea with actually 2 use cases.
The idea in the title on having the PI Integrator SQL database name to be configurable during installation is not something we will move forward on at this time.
However, the second use case mentioned on being able to support more than one Integrator instance on the same SQL server is planned to be supported in the release after PI Integrator for Business Analytics 2018 R2. As always, please feel free to email me if you have any questions!
Add a target that points to a DSN or where you can specify the connection string (including the driver) this would allow to insert in any database that has an ODBC driver for Windows.6 votes
It is not possible to create a “generic” ODBC target because most proprietary ODBC drivers have their own specific reserved strings & functions that do similar things but are named slightly differently depending on the vendor. These functions must be specifically translated to work with the PI Integrator. To date, we support writing to PI Views, Oracle, and SAP HANA via the ODBC standard. If there is a need for a specific type of ODBC driver, please create a new idea and we will look into it. Thanks!
We have a large team that builds and manages our PI system. I need a way to tell users an asset is used by PI Integrator for publishing data so they know not to delete or edit that asset. For our PI Server, we use custom PI Point attributes to track what systems use a given PI tag. It would be nice if we could do the same with AF properties to track which AF elements are used by PI Integrator.1 vote
The use case makes sense. However, adding more data into the system purely for this use case is not an ideal solution as it will unnecessarily add overhead to performance of the AF server for any downstream clients. If this is a need you have, please email me directly so that I can follow up and get more context on the use case.
Being be able to delete one View after the data is posted to the destination. The use case would be a one time needed data exportation to a database. This way the list of views will be better managed. There would be no need of waiting until the publication is performed.1 vote
We cannot assume all users want their views automatically removed. A run-once view persists for several reasons. 1) If the shape is useful (e.g. for a machine learning algorithm based off the exploration data), it can be reused to create a new view. 2) After a view runs, it is subject to licensing terms of unique data streams used in the last 7 days.
- Don't see your idea?