SQL Doc - 2.1
Working with projects - SQL Doc
Whenever you document your databases, you set up a project.
You can create a new project each time you want to document your databases. Alternatively, if you will always be documenting the same database objects, you can save the project. You can then open the project file at a later date or run it from the command line.
SQL Doc project files are saved with the extension .sqldoc
Alternatively, you can document a database by right-clicking in the SQL Server Management Studio Object Explorer.
SQL Doc stores the following information as part of the project:
- SQL Server connection
You can edit the connection details as part of the project configuration.
- databases and objects to document
For more information about adding and removing objects from a project, see Setting up the documentation
- project and copyright information included on the project information page and footer of the generated documentation
You can edit this information as part of the project configuration.
You specify the format for the generated documentation and the location that documentation is saved in when you generate the documentation. If you save the project after you generate the documentation, SQL Doc stores the settings that you specify and uses the same settings as defaults next time you generate documentation for the same project.
Editing project configuration
To edit a project's configuration:
- If the project is not currently open, click
Open Project. - Click
Edit Project to open the Project Configuration dialog box.- The Documentation Setup tab contains settings that specify information that is included in the generated documentation:

Project name is displayed on the project information page of generated documentation, and on the title page of documentation in Document (.doc) format.
Project description is displayed on the project information page.
Include SQL creation script in generated documentation: choose whether the script is included in the documentation. For example, if you are going to print the documentation, you might want to exclude the script to make the documentation shorter.
Copyright text is displayed in the footer of generated documentation; if you specify a Copyright URL, the copyright text is included as a hyperlink.
Author is displayed on the project information page and the footer of all generated documentation, and on the title page of documentation if you generate documentation in Document (.doc) format.
You can change the default copyright information used by all projects on the Application Options dialog box, if required.
- The Connection tab contains details of the SQL Server connection for the current project.
- The Documentation Setup tab contains settings that specify information that is included in the generated documentation:
- When you have edited the settings as required, click OK and then click
Save Project on the SQL Doc toolbar to save your changes.
See also |
Was this article helpful?
SQL Doc
- Logging and log files
- Database description runs off page (Version 1.x)
- Changing the project save location (Version 1.x)
- Assertion failure outputting in CHM format
- No database objects are visible for databases using compatibility level 70
- Can't see database objects
- SQL Doc fails with 'Object reference not set to an instance of an object'
- Retaining CHM documentation source files
- Unhandled exception: input string was not in a correct format
- Minimum database permissions required for the user running SQL Doc
- SQL Doc database object description persistence
- Installing HTML Help Workshop fails silently
- Unable to cast object of type 'bn' to type 'bh'
- Logging and log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Doc
- Activating your products
- Activating your products
- Getting help offline
- SQL Doc release notes - version 2.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SQL Doc