We've received error reports appearing during metadata import from DB2 and Redshift. These issues are resolved in Dataedo 8.0.1.
A few errors were reported related to ERD manipulation in Dataedo 8.0. These issues are resolved in Dataedo 8.0.1.
We've updated frameworks used in the development of Dataedo and refreshed the UI. Higher display scaling should no longer make Dataedo unreadable. This also allowed us to fix multiple hard to replicate issues that some users encountered and unlock additional options for improvements in the near future.
Multiple users asked us about the option of including tables in rich-text descriptions. Previously it was possible to paste a table from another spreadsheet, but with limited formatting options.
Dataedo 8 adds an option to create and format a table directly in a rich-text field.
When creating user-defined relations, most of the time the column used for the PK side is the column on which the primary key is specified. They are now suggested by default when creating a user-defined relation, and if the table on FK side has columns with the same name, they will be suggested too!
We're adding support for new versions of metadata sources. Dataedo 8 now supports:
IBM BigSQL - new connector
Amazon Redshift - support for native connection, no ODBC required
MariaDB version 10.3 - support for new version, added support for system-versioned tables
MySQL 8.0.16 - support for new version
Oracle - added support for triggers on views, more schemas can now be imported simultaneously
Percona MySQL 8 - support for new version
SQL Server 2019 - support for new version, added support for triggers on views
Snowflake - added support for procedures
Until now, customized templates were independent of the source template. This could cause issues since when new features were added to the standard template, they wouldn't automatically be included in custom templates.
Templates created in Dataedo 8 onwards will automatically update their base parts. However, this will require re-creating the templates (we promise it's the last time!).
When sharing exported documentation, especially with databases hosted online, showing host and database name can be a vulnerability. It is now possible during export to hide this information.
Previously, search in HTML export by default checked only object names. An additional option had to be set to also search column names. This setting is now checked by default.
Dataedo 7 allowed for exporting comments to database schema for:
SQL Server
Oracle
Azure SQL Database
Azure Synapse Analytics (formerly SQL DW)
Now, we added this functionality for following connections:
PostgreSQL
DB2
Snowflake
Amazon Redshift
Search tab now correctly searches business glossary terms
Schema change tracking now correctly scrolls even long scripts
HTML Export should now display source documentation for business glossary data links
HTML export should now display term type correctly
Improved search for data links from business glossary terms
Fixed an issue where removing a custom field could cause the app to crash
Fixed an issue where sorting a closed list custom field could make it display incorrect values
Multiple other fixes and UI improvements
Fixed an issue with Oracle import checking access to DBA tables
Fixed an issue with adding business glossary links on screens with display scaling
Fixed an issue with connecting to SQL Server without encryption support (e.g. localDB)
Added support for Oracle 18 and 19
Fixed an issue with HTML export from file or Azure repository
Fixed an issue with Redshift import
Fixed an issue with unique key column ordering
Fixed an issue with copying data to clipboard in parallel with other applications accessing it
Fixed an issue where db_owner role was checked incorrectly during server repository upgrade
Fixed a graphics issue when switching between objects from the search tab
Fixed an issue with marking relations as deleted on SQL Server
Fixed an issue with saving the SID/Service name connection setting in Oracle
Fixed an issue with excluding objects from import on MySQL
Fixed an issue with hiding a newly created relation on an ERD
Multiple other fixes and UI improvements
Manually classifying data based on their sensitivity is an arduous task. To make it easier for our Enterprise users, we've added the Data Classification feature to Dataedo 7.5. When run, it suggests column classification based on their name, title, linked business glossary terms, and classification of other columns with the same name.
Docs: Automated Data Discovery and Classification
Some of our Enterprise users signaled that 40 custom fields limit may actually be to low for them. We're increasing it in Dataedo 7.5 - now Enterprise users can add up to 100 custom fields.
With so many custom fields, keeping track of which row you're looking at may be complicated. To solve this, we're adding an option to lock UI columns to most of our grid views. Just right-click a column's header, choose the Lock column to the left option, and it will be always visible when scrolling. To unlock the column, choose Unlock column from the same menu.
Sometimes you may want to export comments or extended properties to your database in different hours or from a different account than you use in Dataedo. To solve this, we've added an option in the Export comments/extended properties form to only generate the DDL script instead of directly exporting the comments. The script can then be copied (just click the Copy all link) and run outside of Dataedo.
Creating a new term based on a column now seeds the term with column's description
Improved Business Glossary responsiveness
Fixed some graphical issues when switching from Business Glossary to other documentations
Added an option to connect to Oracle with SID rather than Service Name
You can now search for objects using schema.name notation
You can now select your repository from a database list rather than manually type its name
Multiple other fixes and UI improvements
Enterprise users can now export Business Glossaries to HTML. Note that each person accessing the export should have either an Enterprise or Enterprise Viewer license (calculate).
We've made some changes to our license agreement regarding trial use, and added information about viewer license for users of Business Glossary export.
Till now, Dataedo blocked connections when no password was specified - a reminder to type the password in was displayed instead. However, since some DBMS allow creating users with no password requirement, from Dataedo 7.4.2 it is possible to connect to databases with blank password.
Fixed an issue with documentation name display in HTML export
Fixed an issue where HTML export from commandline failed when run from a service account
Fixed documentation order in navigation tree
Fixed an issue with repository version comparison when running documentation copy between repositories
Fixed an error caused by removing a parent term from a business glossary, and then trying to edit it
Many organizations use inconsistent language between departments, which can make communication a lot harder. To solve this issue, we're introducing Dataedo Business Glossary for our Enterprise users.
With it, no one will mistake customer for a client or consumer, and everyone in your organization can be on the same page.
Term types and hierarchy lets you quickly find the terms you're looking for:
You can define links from terms to data assets (tables and columns) related to a particular term:
Or find terms related to a particular table or column:
You can also create term relationships, which show how other terms are related to the one you're looking at:
Find out more in our documentation.
We've completely reworked how HTML export works in Dataedo:
You no longer have to choose between local and hosted templates
Export time has been greatly improved, especially for bigger documentations
Initial loading of the file is shorter
The pages are more responsive
Multiple bugs have been removed
The HTML Export is now a single page application rather than a set of static HTML files as previously.
Note that these changes make old custom templates incompatible - they need to be recreated from the current template.
Some of our users contacted us saying that they're using CLR (assembly) functions and procedures in SQL Server, which were not previously imported by Dataedo.
In Dataedo 7.4 we've added support for CLR functions and procedures, and they should now correctly import.
The password to the repository can now be saved
Improved SQL Server import times
Solved issues related to updating MySQL documentations with a renamed schema
Pages opened from Search tab are now more responsive
Custom fields with number type are now sorted as numbers rather than text
Solved multiple other reported issues and bugs