Most today's database engines do not support foreign keys across databases, servers and engines and that would be very useful to understand data. See how you can document them with Dataedo cross-database relations.
Too often, developers produce database documentation containing just a schema information - table and column names, without any descriptions. See a few examples.
Most popular database engines provide option to provide descriptions for schema elements. This article shows how to check if your database uses them.
Quick tutorial on how to view and edit table and column comments with MySQL Workbench.
Long awaited Dataedo 6.0 is finally here.
A few scenarios how you can leverage Dataedo repositories to manage documentation in complex database systems.
A convenient way of browsing object descriptions from within SQL Server Management Studio.
This tutorial will show you how to quickly generate PDF and HTML documentation of your Google Cloud SQL for MySQL databases with Dataedo tool.
I believe you have seen a lot of confusing table and column names and wondered who made them. Here I'm considering the reasons why this happens.
Project is just finished, eveything works great, but then come the moment when you have to document all the stuff you coded during last month. Can anything be worse than it?