Part ofPosture and Discovery
Query-Derived Data Relationships
See Which Database Columns Belong Together
Reveal connections that the schema alone can miss, then use the relationship map to keep discovery and masking aligned across related fields.
- Find hidden links
- Follow sensitive data
- Protect related fields
The hidden relationship problem
One value can appear in many places without a declared link
The same customer ID, account number, or other sensitive value can appear across several tables without a declared key connecting every copy.
DataSunrise builds a Table Relations model from database structure and the way applications use the data. Instead of reviewing columns in isolation, teams can see the surrounding data model before deciding what to discover or protect.
How it works
Build and use a relationship map
DataSunrise combines declared structure with observed behavior, then lets teams review the model before using it.
-
Evidence
Learn how columns connect
Analyze keys and constraints, query history, database objects, and JOIN or WHERE activity.
-
Model
Review Table Relations
See associated columns in a visual model and add or correct relationships with business knowledge.
-
Action
Use the map in discovery and masking
Follow sensitive data into related fields and include those fields in the appropriate rule or task.
Learn From More Than the Schema
Declared structure
Primary keys, foreign keys, and other constraints show the relationships already defined in the database.
Stored database behavior
Query history, views, functions, and stored procedures reveal connections used by applications.
Live application activity
A Learning Rule can observe JOIN and WHERE activity as applications query the database.
Team knowledge
Operators can add or correct relationships that cannot be inferred from technical evidence alone.
Keep Discovery and Masking Aligned
Reveal related sensitive data
When Sensitive Data Discovery finds a protected value, Table Relations can show associated columns that deserve review.
Protect connected fields together
For Dynamic Data Masking or Static Data Masking, DataSunrise can point to known related columns so operators can include the relevant copies in the same rule or task.
Preserve non-production structure
For static masking, Table Relations help process related tables in the order needed to keep the target usable.
Frequently Asked Questions
What does "query-derived" mean?
It means DataSunrise can learn a relationship from the way database queries join or filter columns, including relationships that are not declared as keys in the schema.
Does DataSunrise change database constraints?
No. Table Relations are stored inside DataSunrise. Learning and editing the model do not add or modify keys in the source database.
Does it map relationships across different databases or cloud services?
No. A Table Relations model belongs to one configured database instance and maps relationships among its tables and columns.
Map the right workflow