SQL Doc
Latest version: 2.1
Knowledge Base
Can't see database objects
Category: Troubleshooting & error messages
Date: 21 Apr 2009
Product: SQL Doc
Why can't I see all of my database's schema objects in SQL Doc?
SQL Doc fails silently if there is some metadata in the database that it doesn't understand.
Since SQL Doc shares the same schema registration components with SQL Compare, it is possible to use SQL Compare to pinpoint more specifically which objects are not understood by SQL Doc. SQL Compare will display an error message during the database comparison which will help to find the specific type of object that is causing the problem.
If a problem is found, you may check the database for consistency using SQL Compare and adjust accordingly.
SQL Doc can also exhibit this behavior when the database being documented is compatible with SQL Server 7 or less, or when the metadata is inconsistent, which can be diagnosed in SQL Server Management Studio using the query "DBCC CHECKDB" run in the context of the database which can't be documented.
Document ID: KB200807000277 Keywords: SQL,Doc, database, objects,empty,visible
Was this article helpful?
Using SQL DocSQL 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
