Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Tell us more
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Automatically remove data from continuous views

As an engineer using PI View or SQL writers for a report, I would like option to remove data older than a certain cutoff. For example, a continuous view is used to generate data for a report on the last 8 hours. Data older than that are no longer needed for the report and should be removed to avoid unnecessarily large tables. One workaround with Text and Hadoop writers is the Append Timestamp option, but there's no ability to remove data from other targets.
  • ADMIN RESPONSE
    Aug 16, 2022
    For supporters of this idea, what is the downstream client tool that consumes the data prepared by the PI Integrator? Is the concern about disk space or how to only display data for a specified time range? For the former, this seems to be a different type of "rolling" reporting use case that we do not currently have a solution for. In the mean time, as Rory mentioned below, a stored procedure on SQL would work if this idea is intended for SQL writers. For the latter, is it possible to create “rolling timespans” for your graphs, reports, tables, etc.? For example, here’s a video on how to create calculated measures for a table based on last day or month of data: youtube.com/watch?v=NevFWL2JoMU
  • Attach files
  • Guest
    Reply
    |
    Aug 16, 2022
    Thanks for bringing this in. Hans Bleijendaal
  • Guest
    Reply
    |
    Aug 16, 2022
    I agree with this use case. For SQL targets, you could create a stored procedure to delete data older than a certain time, and then you can run it with SQL Agent. Not the most ideal scenario, but it works. Stack Overflow has a good example for deleting data here: https://stackoverflow.com/questions/1588722/delete-items-older-than-a-day-sql-server
  • Guest
    Reply
    |
    Aug 16, 2022
    As a PII4BA user I need to maintain on the target database only the data corresponding to the specified time range, older data should be deleted when new data is inserted.
  • Brent Bregenzer
    Reply
    |
    Aug 16, 2022
    Most customers who've asked about this are concerned with the former. They would prefer the Integrator didn't produce ever-growing tables when they only need the last 6mo, 1y, etc. of data online, and they consider it an added burden to manage stored procedures to trim the tables.
  • Kelsey Bobeck
    Reply
    |
    Aug 16, 2022
    This feature would be beneficial to minimize storage needs (and therefore cost) in Redshift, as the Redshift endpoint we publish to is a "buffer" storage point before the data gets picked up by a glue job. Once it's picked up, we don't need the data anymore. However, applying purge processes on a large number of tables could be challenging and it would much easier if this was done through the Integrator.
  • PowerPI
    Reply
    |
    Aug 16, 2022
    I have a view that writes a text file every 10 minutes. My client has an automated system to pull in the data every 10 minutes. After that, the file/data is not needed. I would like there to only be one file and for Integrator to overwrite the existing file/data. I currently have it set to not append timestamp and there is only one file. However, it keeps adding data to the file. Thanks
  • Lebretonp
    Reply
    |
    Aug 16, 2022
    Hello, We have also the same need (drop data before the execution query in continous mode) Regards, Pascal
  • aclaus
    Reply
    |
    Aug 16, 2022
    I have come upon this topic again after upvoting it before. My specific issue now is that we have databases growing exponentially larger than they need to be. We require seven days of data and only seven days of data for Power BI dashboards and we sit at about 350 days of data currently in an Oracle database. Additionally, I use PI for BA to output to .csv files and only need one value for multiple data points, but have 7 days of that data because PI for BA appends all files, it does not overwrite the file.