Full site membership is required for this article. Already a full member? Login here. You currently have a guest membership. You can upgrade to full site membership here (free trial available). Review: DB Documentor from Elzaris Technologies   Article Abstract: (Stephen Wynkoop) From disaster recovery to compliance situations, documenting a database structure, dependencies and making a meaningful and easy to use map of your database has long been a problem. Elzaris Technolgies seeks to change this with their DB Documentor product, designed to point and click create documentation and full DDL scripts that you can use not only for information, but for real recovery of your systems should the need arise. This review goes into whether they've hit the mark with their new product.   Read this article...

Related Articles - For Members. All Articles By Author Understanding Yukon Schema Separation SQL Server 2005 - Schema Definition Schema Wars: XML Schema vs. RELAX NG Undocumented SQL Server 2005 XML Objects Regulatory Compliance 101 for the Overworked DBA XML integration with ADO+ Let's examine the basics of XML Archiving Oracle Data in easily restorable non-Oracle structures Part 2 of 2 The AdventuresWorks of Yukon Jack: Schema Separation and the SQL Server 2005 Authorization Model Microsoft SQL Server 7.0 "Sphinx" Overview

RE: Review: DB Documentor from Elzaris Technologies
by lana latinsky (posted: 1/26/2007 4:32:18 PM)
Hello, Stephen. I read your review a couple of months ago, and your opinion actually helped me to choose the db documentation software for our needs. The document generated looks great! The only problem with this tool is that when run on a large database it will abort with:
the connection was lost during the generation process error.
Their support person was very helpful. He supplied me with a new executable when they figured out their program did not handle multiple rows for the same objectid in the syscomments table.
But the lost connection is still a problem unless I uncheck the dependencies check box. They narrowed it down to a situation when a database with a large number of objects (for example: table is referenced by multiple foreign key constraints ) has to be scripted .
Their program will timeout since it cannot generate all dependencies in time allocated for this process. I haven't received anything from them yet saying when it will be fixed. Thought you would want to know ...
thank you