Document missing relations and unique keys
Even though almost all relational databases enable defining foreign keys (relationships between tables), in many cases they are not defined. This is especially the case in data warehouses, applications using ORM technologies (object-relational mapping), old databases and databases designed by teams relaxed about data integrity.
Reverse engineer legacy databases
If you have to develop or maintain legacy databases and need to understand relations between tables and views. Dataedo can help you with the task. Together with grouping objects into modules ability to document missing foreign and unique keys and generating Entity Relationship Diagrams is a great tool set for the job.
Document missing foreign keys
To document foreign keys just add another row in the list of table or view relations tab, choose object and specify columns and save. It's as simple as that.
Document missing unique keys
Information that some values are supposed to be unique is very important and useful. Most relational databases enable setting unique constraints for specified columns (or group of columns). This feature, however, often is not or cannot be used (for instance, when data is dirty).
With views too
Popular relational database systems don't allow creating foreign or unique keys for views. quite often, especially in reporting applications, you query data using views that implement complex logic. If you want to join with views you need to be sure which views and columns to use, which columns can be used as primary keys, which columns are unique. Dataedo gives you ability to document such relations and constraints for views.
Auto generate ERDs
Dataedo shows relations on Entity Relationship Diagram that come from database or were added in your documentation.