Profiling a Data Agent database
A database profile is a thorough analysis of the data and its structure. Each table has its own profile.
Creating and updating the database profile
The Data Agent consults the profile whenever it needs to understand the content or structure of a table. For example, when it adds data to a table, the Data Agent uses the table profile as a guide. You can also prompt the Data Agent to use a profile to guide data generation. For example, for a live connection database, you can generate data to one database connection based on the profile of another database connection.
When it needs to use profile information, but there is no profile, then the Data Agent automatically creates one.
The Data Agent also automatically updates the profile to reflect changes to the data structure. For example, if you add columns or if you make changes to the distribution of values, then the Data Agent updates the profile.
To manually profile a database, prompt the Data Agent. For example:
Create a profile of this database.
Viewing a table profile
To view the profile information for a table:
For a live connection database, click the database connection to display the profile for.
In the database table list, click the table.
In the table heading, click the findings icon.
What's in a table profile?
For each table, the profile includes:
A description of the database.
The DDL for the table.
Correlation of columns. For example, a transaction date and transaction identifier are likely to be tightly correlated. Or the total cost of an order is the sum of each order item cost times the order item quantity.
Cardinality of column values. For example, most orders have 1 item, fewer orders have 2 items, and even fewer orders have more than 2 items.
Constraints on columns. For example, the same order cannot have a duplicate product identifier. All timestamps must use the ISO 8601 format.
Distribution of column values. For example, customer addresses are distributed across 20 states.
Last updated
Was this helpful?