Data Profiling–Security Considerations

Default Behavior

By default, when installed, Dataedo does not allow you to save profiled data in the repository. Users can only execute profiling in Desktop and analyze results in a window as long as it's open. This behavior can be changed for the specific repository to Disabled or Read/Save.

How to Disable Data Profiling?

You can disable Data Profiling by setting the DISABLED value in the dbo.configuration repository table.

Read more in the Data Profiling Configuration article.

Where Is the Data Saved?

Data collected during profiling is saved in the repository only when the user performs a save action. The data is saved in the column_values table, and some data can be found in the value_min, value_max, value_string_min, and value_string_max fields in the columns table.

Metadata (like calculated averages or row counts) is saved in new columns in the tables, tables_stats, and columns tables. In case you are thinking about saving GDPR-relevant data, please consider adding the above as places where your GDPR data might be stored.

Find out more about which columns store what data in the Dataedo Repository Schema Documentation.

How to Remove Data Profiling Data?

To remove saved data from the database, you should use the built-in Dataedo Desktop option of Clearing Profiling Data on all tables for which Profiling Data is saved. Alternatively, you can access the repository database and purge the column_values table and clear the correct columns from tables, tables_stats, and columns values.