Schema Detective is useful for a range of database-related roles. Anyone who needs to find data inside the database or try and find relations between database tables might find Schema Detective highly productive.

Database best practices dictate setting of Primary-Keys and Foreign-Keys to ensure referential data integrity. However, in many real-life environments, Foreign-Keys are not defined leaving the application responsible for maintaining referential data integrity. In common business scenarios, a non-developer (e.g. security administrator, DBA, architect) is asked to determine the referential relations between database tables. Unfortunately, in the lack of foreign-keys this may become an arduous task. Schema Detective can bridge this gap by detecting application referential integrity relations, which are not defined in the database.

Schema Detection is a tool that specializes in database ‘detection’. As such, it has features which JumbleDB lacks, namely: searching within an entire database instance (server) and selective exclusion of schemas (databases) from the search.

Schema Detection is a tool that specializes in database ‘detection’. As such, it has features which JumbleDB lacks, namely: detection of cross-database relations and generation of foreign-key creation scripts.

Not in the current version. However, this feature is on our wish-list and will be supported in a future version.

Yes. Schema Detective may locate values inside large text fields, for all supported RDBMS.

Schema Detective is officially supported only for Oracle versions which are supported by Oracle corp. However, you might try running Schema Detective against Oracle 8.1.7 – results may be quite satisfactory.