We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

BRD Files


1 comment

  • Avatar
    Adrian Williams

    When a data flow is run each node caches the output data for its output pins in a separate intermediate data file (.brd file). The benefit of this mechanism when building a data flow is that you can re-run a node without having to re-run all of the upstream nodes. However, the intermediate data for ad hoc executions is not automatically purged by the system so if you have multiple users each with many data flows the intermediate data files can consume disk space on the server. The system allows you to manually purge the run data for a data flow to free up space when you no longer need to retain access to the intermediate data.

    When using a schedule to execute a data flow each run creates its own set of run data. Unlike with ad hoc executions of a data flow, the state of each scheduled data flow execution is retained by the system (allowing you to access the previous runs' information). System configuration settings allow you to specify how long the scheduled execution run data should be retained for (in terms of the number of days and/or the number of previous runs). The system then automatically purges execution run data that is outside of the retention criteria. 

    See the following article for suggestions on how you can free up disk space. The article also provides some tools to help monitor available disk space and to clear up other data such as log files.



    Comment actions Permalink

Please sign in to leave a comment.