Search
Home
Articles
Backup
Books
Certification
FAQ
Products
Replication
Scripts
Seminars
Training
TSQL

MSDN Fourms
Fort Worth SSUG
Oklahoma City SSDG

Resume

Champion Valley Pens

SQL-Programmer 2.2 1 2 3 4 5 6 7

The third major module is the Documentor.  This module by itself is more than enough justification to purchase SQL-Programmer.

Sfi13.gif (18942 bytes)

Getting all of the different reports would take a few pages.  I highly encourage evaluating this to get a look at the reports.  I investigated the stored procedure and trigger reports simply because that is what I needed at the time.  The procedure report begins by listing all of the variables and parameters for the procedure.  Then there is a listing of the text of the procedure.  Finally at the end is a listing of any references or dependencies.  The same holds true for the trigger reports.   This goes a long way to providing virtually all of the documentation you could need generated directly from the database. 

Sfi14.gif (17935 bytes)

The one drawback at this point is that you are bound to paper.  There is no support to save the reports to a file or publish them as HTML.  Although I've been assured that publishing reports to HTML is one thing that is at the top of the list for the next release.  There is also no capability to customize the header or the footer.   While this is sufficient for most people, generating documentation and turning it over to a client that has SQL-Programmer 2.2 as the footer on each page looks rather unprofessional.

SQL-Programmer 2.2 1 2 3 4 5 6 7

Michael R. Hotek

All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.