Is it possible to control which nodes are expanded when the chm file is opened? Our project has 2 SQL Servers documented and currently the first node (which is the first server) is expanded but not the second. Thanks

I have a project that documents 2 SQL Servers. I would like to place the documentation for each server inside a seperate parent folder that contains other documentation relative to that specific server. This content will be added by me manually. Is there a way to filter which DB documentation goes into...

I've included comment headers similar to the following into the top of new stored procedures: /*====================================================================== -- ##SUMMARY Put_a_brief_summary_of_the_object_here_single_line_only -- ##REMARKS Enter_any_notes_about_the_object_can_be_multi_line...

I am in the process of creating functional database documentation intended to describe the usage of tables and columns. The audience does not need to see Indexes, Relationships, Objects that <table> Depends On, SQL, or See also sections for each of the tables. Is there any way to exclude these...

I have created some extended properties on database tables and columns (e.g., "Appropriate Use", "Caveats", etc.) and I want them to be picked up by Document X! How do I specify that I want the extended properties to be documented? Thanks, Chris

I would like to display the date on which the project was built in my database templates. Is there a way of doing this? I can easily get the global template date but this isn't necessarily my build date. Thanks

Take a look at this post: http://www.innovasys.com/cs/forums/p/31/35.aspx#35 Looks like using (local) instead of localhost is the solution. SQL Server isn't always happy with localhost but should always be happy with (local).

I want to add descriptions to database roles in SQL Server and have used sp_AddExtendedProperty to add an MS_DESCRIPTION property to various roles but DocumentX does not seem to pick these up. It works fine for tables and fields but not for any other object. Has anyone else had any luck with this?

It looks as though "(local)" is a better alternative to "localhost" and should work in Document! X and other places where the server name is required. Richard Sloggett Innovasys http://www.innovasys.com