SQL Doc^™

When you select a database for which you are not the database owner, SQL Doc displays only those objects for which you have been granted permissions.

SQL Doc does not document extended stored procedures.

If you are documenting a SQL Server 2000 database that contains an encrypted user-defined function, stored procedure, trigger, or view and you have system administrator permissions, SQL Doc decrypts the object and you can view its internal SQL. However, SQL Doc cannot decrypt views, stored procedures, functions, DML triggers, and DDL triggers that are encrypted in a SQL Server 2005 database. Therefore, SQL Doc cannot document the creation SQL for encrypted objects.

SQL Server severely restricts access to certificates, symmetric keys, and asymmetric keys. Consequently, SQL Doc cannot document all of the properties for a symmetric key.

SQL Doc documents only one stored procedure for groups of numbered stored procedures.

Yes, but to edit an MS_Description extended property, you must have the appropriate permissions. You can type up to 800 characters for your description.

By default, SQL Doc creates your database documentation using HTML with frames. SQL Doc generates database documentation with frames much more quickly and the file sizes are smaller. You are recommended to use this setting if you are documenting large databases.

To create database documentation without frames, change this setting to HTML without frames.

To create database documentation in compiled HTML Help format (.CHM), change this setting to Microsoft HTML Help (.CHM). Note that you must have Microsoft® HTML Help Workshop installed on your computer to create a .CHM file; a free download is available from the Microsoft Download Centre.