SqlSpec 4.0

SqlSpec 4.0 can make you easily use it  for any SQL Server, Analysis Server, Oracle, DB2, Sybase ASE, Sybase SQL Anywhere, MySQL, PostgreSQL, Informix IDS, VistaDB, ENEA Polyhedra, or MS Access database. Given one or more connection strings, SqlSpec will generate documentation about all the tables, views, stored procedures, triggers, indexes, constraints, schemas, assemblies, CLR procedures, xml schema collections, synonyms, symmetric and asymmetric keys, user defined types, and user defined functions in your database.

It will also tell you what the dependencies are (which tables point to other tables via foreign keys, which tables are used by which stored procedures, etc.) It will show the code for each trigger, view, user defined function, check constraint, and stored procedure in the database. SqlSpec generates output in HTML and CHM format. You can configure it to add external objects (such as web pages, COM objects, and other external code) to the documentation as well. You can even incorporate such objects into the dependency graphs generated by SqlSpec.

With SqlSpec, it is easy to keep documentation in sync with the actual database, since you can just run SqlSpec on your databases and your documentation gets updated.

Major Features:

1. Show scripts for all objects documented.
2. Ability to add your own branding logo (headers and footers) to each page in the documentation.
3. Run as a console application, useful for automating SqlSpec to generate documentation for your databases on a schedule, or integrating SqlSpec into your development process.
4. Supports XML comments added to your stored procedures, user defined funtions, views, and triggers, similar to XML comments in C# code. These comments are parsed by SqlSpec and the content is placed in your documentation.
5. Include external objects (such as web services, web pages, and other components) in the documentation. Specify dependencies of external objects on database objects and they will be included in the dependency graphs.
6. Creates data model diagrams where any database object (or external object) can be represented.
7. Specify an exclusion list so that certain objects (or just the SQL code for them) can be excluded from the documentation.
8. Specify a custom navigation hierarchy to include arbitrary HTML files in the generated CHM.
9. Generate dependency and primary/foreign key graphs. Such diagrams are much easier to understand at a glance than a flat list of dependent objects.
10. Generate a call graph for sprocs and udfs that call other sprocs and udfs.
11. Fine control over what object types are documented.
12. Support for every major DBMS in a single affordable tool.

• SQL Server,
• Analysis Server,
• Oracle,
• DB2,
• Sybase ASE,
• Sybase SQL Anywhere,
• MySQL,
• PostgreSQL,
• Informix IDS,
• VistaDB,
• ENEA Polyhedra
• MS Access. . .
  

Requirements:

• .NET Framework 2.0 required on client