ApexSQL Doc Changelog

What's new in ApexSQL Doc 2022.01.1179 Patch

Jun 8, 2023
  • Fixes:
  • 200176: "It may have been moved, edited, or deleted" error is encountered when generating documentation for a server that has a four-part DNS name in its name
  • 203577: The application freezes and becomes unresponsive when loading an SSISDB catalog that contains more than 50 SSIS packages
  • 203595: Loading SSIS packages from the SSISDB catalog is slow
  • 180942: "This page can't be displayed" error is encountered when the SSIS package is documented in CHM output file format
  • 192963: Missing Headers in Doc and HTML output file formats
  • 221383: SSIS packages from the SSISDB catalog will be saved in the "Temp" folder when the documentation process is done
  • 220647: "Can't reach this page" will be shown in the CHM documentation when the SSIS package which contains "%" in Description is documented
  • 211540: "Could not load file or assembly 'Microsoft.Identity.Client'" error is encountered when trying to connect to the Azure server with Active Directory - Integrated type of authentication
  • 211653: "Could not load file or assembly 'Microsoft.Identity.Client'" error is encountered when trying to connect to the Azure server with Active Directory - Universal with MFA type of authentication
  • 211714: "Could not load file or assembly 'Microsoft.Identity.Client'" error is encountered when trying to connect to the Azure server with Active Directory - Password type of authentication
  • Changes:
  • The activation model is switched to Subscription
  • The application does not support integration into SQL Server Management Studio 2012, 2014, and 2016 versions
  • The application does not support integration into Visual Studio 2010, 2012, 2013, and 2015 versions
  • Known issues:
  • "The 'ApexSOLDocJnstPackage' package did not load correctly" error is encountered when the Visual Studio 2019 16.7 version is started
  • Generated Word and PDF files do not contain any data when documenting Tableau Online and Tableau Server Version 10 and above

New in ApexSQL Doc 2020.03.1156 Patch Release (Mar 2, 2021)

  • Fixes:
  • 200176: "It may have been moved, edited, or deleted" error is encountered when generating documentation for a server that has a four-part DNS name in its name
  • 203577: The application freezes and becomes unresponsive when loading an SSISDB catalog which contains more than 50 SSIS packages
  • 203595: Loading SSIS packages from the SSISDB catalog is slow

New in ApexSQL Doc 2020.03.1151 (Dec 16, 2020)

  • Fixes:
  • "Couldn't connect to SSISDB catalog on server" error is encountered when trying to connect to the SSISDB catalog which contains multiple SSIS projects with the same name
  • "SSIS diagram is missing" warning is displayed when SSIS packages contains a data flow diagram
  • Data flow diagram title is not readable when it includes multiple words

New in ApexSQL Doc 2020.02.1150 (Nov 16, 2020)

  • Fixes:
  • 184180: The version of the SQL Server does not contain all information for SQL Server 2014 SP3 in the CHM output file format
  • 187465: "Can't reach this page" message is shown in the documentation when trying to open the Header, Body, or Footer items in the CHM output file format when documenting SQL Server Reporting Services (SSRS)
  • 190145: Parse error: [Incorrect syntax near '.'] at [position: 99367, line: 1511, column: 81] is encountered while creating documentation for SQL procedure that contains the Date add function
  • 185887: Object names are not fully visible for the SSIS data flow diagrams in a created documentation
  • 178916: Linked servers are not shown under the Server info section in a created documentation
  • 189689: Tables are not alphabetically sorted for PDF, DOC or DOCx output file formats
  • 192961: "There are no objects in Linked servers collection" information is shown for Linked servers under the Server objects tab

New in ApexSQL Doc 2020.1.1135 (Nov 2, 2020)

  • Enhancements:
  • SQL Server Analysis Services compatibility level for Tabular models 1500 support
  • The Activate button is added under the Resources menu in SQL Server Management Studio and Visual Studio
  • Application telemetry now collects anonymous data on the use and performance of applications and application components
  • New ApexSQL Updater allows users to configure advanced updating settings of all installed ApexSQL products
  • Fixes:
  • Unable to document Project parameters from the SSISDB catalog
  • All objects are checked after a database is filtered by object type and object name, and the Check all option is checked
  • The application does not document the Database description in a Tabular SSAS database
  • The header is missing in the CHM documentation when the identity between two tables is created
  • The header is not aligned with the data in the CHM file format
  • The previously documented Analysis services are documented along with Integration services even though Analysis services were not selected for the documentation process
  • Changes:
  • The application is now part of the ApexSQL DevOps Plus Toolkit for SQL Server bundle
  • Error handling and send logs functionality has been modified

New in ApexSQL Doc 2019.1.1123 (Dec 16, 2019)

  • Enhancements:
  • SQL Server 2019 support
  • Markdown output format is added under the File format tab in the Output options section
  • SSIS package store (SQL Server 2019) is added under the Add integration service package dialog
  • Fixes:
  • Descriptions for SSAS tables are not generated in the documentation for all output formats
  • When two SQL jobs with the same name are scheduled, only one is executed and documentation is created
  • "Too many file packages are selected for documenting" error is encountered when more than 25 packages are selected for documentation
  • Changes:
  • /performance_intensitive_items switch is renamed into /performance_intensive_items

New in ApexSQL Doc 2018.06.1100 (Oct 9, 2019)

  • Enhancements:
  • Visual Studio 2019 integration support
  • Fixes:
  • Document server properties are not documented in the PDF and DOCX output file formats
  • "Could not load file or assembly" error is encountered when the Template check box is right-clicked in the Naming tab from Output options
  • "Couldn’t connect to SSIS AcriveXScriptPackage.dtsx" message is shown when trying to connect to SSIS project file
  • "Object reference is not set to an instance of an object" error is encountered when any ApexSQL Doc command is clicked from main menu in Visual Studio 2017
  • "Could not load file or assembly" error is encountered when the Open button is clicked from the Home tab to open a saved project
  • Roles and Mining structures are not documented on SSAS Multidimensional model
  • The application cannot be uninstalled if any version of SQL Server Management Studio is running, even though the application is not integrated in it
  • The application cannot be uninstalled if any version of Visual Studio is running, even though the application is not integrated in it
  • The application can be integrated into any version of SQL Server Management Studio that is currently running
  • Saved project file can not be opened with double-click on it
  • "Could not find a part of the part" error is encountered when the Server engine is documented with the Linked servers option in the HTML output file format
  • Cannot change database table and column description at the same time when using the Extended property editor
  • Graphical dependencies option is not checked when clicked under the Database options tab
  • Dependency layout option is changing when the Graphical dependencies option is checked under the Database option tab
  • Hierarchical dependency layout is not default layout under the Database options tab
  • Server object options are not reverted to defaults values when a new project is initiated
  • "Can't reach this page" error is encountered in documentation for the DDL triggers graphical dependencies
  • "Object reference is not set to an object instance" error is encountered while generating documentation for tabular model under the Analysis services
  • The application cannot be integrated into any SQL Server Management Studio or Visual Studio version through the silent installation
  • The uninstall confirmation message box appears when the /verysilent and /suppressmsgboxes options from CLI are used
  • SSRS object are being duplicated in generated documentation
  • Missing options to set the Connection timeout for Tableau server
  • Connection to Tableau server cannot be canceled
  • "Could not find any resources appropriate for the specified culture or the neutral culture" error is encountered when generating documentation while using SharePoint farm
  • "Illegal characters in path" error is encountered while generating documentation for Tabular model under the Analysis services
  • Documenting SQL Server instance fails when Alerts exist on SQL Server
  • The application includes snapshots in documentation that are not selected when PDF file format is selected
  • "Object reference not set to an instance of an object" error message is shown for the AW2014Master database in HTML file format
  • "The given key was not present in the dictionary" error is encountered when generating multiple packages of SSIS documentation for DOC and DOCX file format in the CLI
  • "The process cannot access the file" error is encountered when generating documentation for multiple databases in CHM and HTML file format in the CLI
  • Selected server objects are not shown in the Save as automation script window
  • Changes:
  • /analisys_services_databases switch is renamed into /analysys_services_databases
  • /exclude_analisys_services_databases switch is renamed into /exclude_analysys_services_databases

New in ApexSQL Doc 2018.05.1073 (Jun 21, 2019)

  • Software Transaction Agreement is added as a new step in the installation wizard and updated in accordance with https://www.quest.com/legal/sta.aspx

New in ApexSQL Doc 2018.05.1064 (May 16, 2019)

  • Enhancements:
  • SQL Server Management Studio 18 GA integration
  • Visual Studio integration support
  • Active Directory support for:
  • Universal with MFA support authentication
  • Document SQL Server level information
  • Documenting SQL Server Integration Service packages does not require installed SQL Server Integration Services
  • Fixes:
  • ”Object reference is not set to an instance of an object” is encountered when a database is documented in the chm output format with the detailed option preset
  • The CTRL+V shortcut is pasting clipboard text under the Shortcuts tab in the Options window instead of setting it as a shortcut
  • Changes:
  • The application now requires Microsoft .NET framework 4.7.2

New in ApexSQL Doc 2018.04.1022 (Mar 29, 2019)

  • Fixes:
  • "Attempted to perform an unauthorized operation" error is encountered when documenting SSAS Tabular Model with compatibility level 1400

New in ApexSQL Doc 2018.04.1021 (Feb 21, 2019)

  • Fixes:
  • "Could not load file or assembly" error is encountered when the project is saved as an automation script
  • MS_Description is not shown in the procedures in the Extended properties when documenting database in Linked HTML files file format
  • “Method not found: 'DevExpress.Utils.AppearanceObjectDevExpress.XtraRichEdit.RichEditAppearance.get_Text()'”error is encountered when project is saved as automation script
  • The Extend evaluation button does not open default e-mail client when clicked and the application is opened in the Community edition
  • Missing information message when the Extend evaluation button is clicked and there is no default e-mail client

New in ApexSQL Doc 2018.04.1020 (Feb 13, 2019)

  • Fixes:
  • MS_Description is not shown in the procedures in the Extended properties when documenting database in Linked HTML files file format
  • “Method not found: 'DevExpress.Utils.AppearanceObjectDevExpress.XtraRichEdit.RichEditAppearance.get_Text()”error is encountered when project is saved as automation scrip
  • The Extend evaluation button does not open default e-mail client when clicked and the application is opened in the Community edition
  • Missing information message when the Extend evaluation button is clicked and there is no default e-mail client

New in ApexSQL Doc 2018.03.0972 (Oct 17, 2018)

  • Enhancements:
  • Performance has been improved for generating documentation with graphical dependencies up to 350%
  • SQL Server 2019 CTP 2.0 support
  • SQL Server Management Studio 18 integration support
  • Save automation script as a PowerShell script
  • New error handling and send logs functionality
  • Improved application installer with a dark theme
  • Fixes:
  • “Failed to run hh.exe” error is encountered while generating database documentation in DOCX and PDF file format
  • “Dependency Explorer Console has stopped working” error is encountered while generating documentation with graphical dependencies

New in ApexSQL Doc 2018.02.0901 (Aug 2, 2018)

  • Enhancements:
  • Performance has been improved for generating documentation with graphical dependencies up to 350%
  • Fixes:
  • “Failed to run hh.exe” error message is encountered when generating database documentation in docx file format
  • “Dependency Explorer Console has stopped working” error message is encountered when generating documentation with graphical dependencies
  • Application stops responding when adding SSIS or SSRS package from file system
  • Empty documentation is generated when documenting Visual Studio 2017 SSIS packages
  • Application stops responding when generating documentation for multiple databases in HTML file format
  • Application stops progress at 51% when generating documentation with graphical dependencies

New in ApexSQL Doc 2017.08.0824 (Apr 23, 2018)

  • Enhancements:
  • Differential snapshot documentation
  • Fixes:
  • "Failed to run hh.exe" error message is shown when documentation of AdventureWorks2016 CTP3 is completed in docx and pdf output formats
  • When default e-mail client is not MS Outlook clicking the "Send logs" button opens a zipped log file in File explorer
  • SSIS packages from SQL Server Integration Services Package Store 2017 cannot be documented when using the CLI
  • SQL script is missing from documentation in SQL statement section when documenting SSAS databases in chm and html output formats
  • "Object reference not set to an instance of an object" error message is shown when documenting SSRS 2016 Shared data sets and shared data sources in docx and pdf output formats
  • "Object reference is not set to an instance of an object" error message is shown when documenting SSRS 2016 reports in docx and pdf output formats
  • The application repeatedly asks for the activation key when it is started on an Amazon EC2 instance after the virtual machine resources were deallocated and allocated again

New in ApexSQL Doc 2017.07.0796 Patch (Mar 6, 2018)

  • SQL script is missing from documentation in SQL statement section when documenting SSAS databases in chm and html output formats

New in ApexSQL Doc 2017.07.0795 Patch (Mar 1, 2018)

  • Fixes:
  • "Object refference not set to an instance of an object" error message is shown when documenting SSRS 2016 Shared data sets and shared data sources in docx and pdf output formats

New in ApexSQL Doc 2017.07.0793 Patch (Feb 5, 2018)

  • Fixes:
  • "Object refference is not set to an instance of an object" error message is shown when documenting SSRS 2016 reports in docx and pdf output formats

New in ApexSQL Doc 2017.07.0792 Patch (Jan 24, 2018)

  • Fixes:
  • The application repeatedly asks for the activation key when it is started on an Amazon EC2 instance after the virtual machine resources were deallocated and allocated again

New in ApexSQL Doc 2017.06.0779 Patch (Nov 15, 2017)

  • Fixes:
  • Chart pictures are missing from Views section of Tableau site documentation in HTML output format
  • Editing a custom extended property description is not possible if "MS_Description" extended property does not exist for the same SQL object
  • Extended property descriptions for database roles are not generated in documentation
  • Extended property editor takes too much time to open and show all data
  • If an extended property description is updated to be a zero length string the extended property is deleted
  • It is not possible to edit an SQL object extended property description for "MS_Description" if that description contains a zero length string
  • SQL jobs are missing from the "Object type" list in the "Server objects" tab when connected to a database on SQL Server 2017
  • System created database roles are not visible in Extended property editor
  • Wrong return code is shown when encountering an error that the specified intermediary files location is too long

New in ApexSQL Doc 2017.06.0777 Patch (Sep 19, 2017)

  • Fixes:
  • Excessive parameter "alified=" documented in hundreds of rows in SSIS documentation
  • Editing a custom extended property description is not possible if "MS_Description" extended property does not exist for the same SQL object

New in ApexSQL Doc 2017.06.0767 (Sep 14, 2017)

  • Enhancements:
  • CLI support for SharePoint documentation:
  • Include SharePoint farm [/sp]
  • Include SharePoint farm objects [/spobj]
  • Include SharePoint farm options [/spopt]
  • Fixes:
  • Extended property description that contains a zero length string cannot be updated if "MS_Description" extended property does not exist
  • Saving an edited extended property description for a Database is not possible if the previous description contained a zero-length string
  • “Object reference not set to an instance of an object“ error message is shown when trying to document SSIS 2012 project files that contain data flow diagrams in chm and html output formats
  • A batch file can be created in the "Save as batch" window when there is no data source selected in application
  • CLI switch for documenting SSIS packages from SSISDB catalog does not exist
  • The "Execution timeout" value is changed to 7200 seconds when the Defaults button is pressed in "Connection options" window
  • File format tab cannot be opened in "Project defaults" window
  • Multiple database schema snapshots cannot be added at the same when adding them for documentation
  • CLI switch for documenting SSIS project files does not exist
  • Default file name is not offered when saving a project file
  • Parent option is not selected automatically when a child option is selected manually in Database options tab
  • Options window cannot be closed using the ‘Esc’ key
  • The "Refresh extended properties" option in the Database objects tab is not working
  • "Failed to open 'File path'" error message is shown when the process of generating documentation in html output format is stopped
  • "Failed to run hh.exe" error message is shown when the process of generating documentation in doc, docx and pdf output formats is stopped
  • Documentation title is not changed when a custom documentation title is set up in the Naming tab
  • "Object reference is not set to an instance of an object" error message is shown in Extended property editor window when Ctrl + Delete keyboard button combination is pressed
  • File format tab cannot be opened when "Generate documentation" option is clicked in SSMS when connected to an Azure SQL database
  • Saving an edited extended property description for a SQL Table is not possible if the previous description contained a zero-length string
  • Application cannot be integrated into SSMS 2012 and 2014 on Windows 8.1
  • Navigation menu and table of contents are referenced wrong in SSIS documentation in doc and docx output formats
  • SQL tables are not expanded on double click in Extended property editor window
  • The application uninstall process does not detect that SSMS is running if the application is integrated into SSMS

New in ApexSQL Doc 2017.05.0739 Patch (Sep 1, 2017)

  • Fixes:
  • Extended property description that contains a zero length string cannot be updated if "MS_Description" extended property does not exist

New in ApexSQL Doc 2017.05.0738 Patch (Aug 29, 2017)

  • Fixes:
  • Saving an edited extended property description is not possible if the previous description contained a zero lenght string

New in ApexSQL Doc 2017.05.0737 Patch (Aug 8, 2017)

  • Fixes:
  • “Object reference not set to an instance of an object“ error message is shown when trying to document SSIS 2012 project files that contain data flow diagrams in chm and html output formats

New in ApexSQL Doc 2017.05.0732 (Jul 27, 2017)

  • Enhancements:
  • Support for SharePoint Server in doc, docx and pdf output formats
  • Fixes:
  • "No data source is selected for documentation" information message appears when trying to document database schema snapshots, SSAS databases, SSIS project files or SSRS items separately
  • "Specified cast is not valid" warning message appears when trying to connect to SQL Server 2016 SSISDB catalog
  • "Object reference is not set to an instance of an object" error message is shown when documenting SSAS 2016 Tabular databases in pdf output format
  • SSIS control flow diagrams are not shown in documentation when documenting SSIS 2016 packages that contain CDATA section other than DesignTimePropertis in the package source
  • Tableau site documentation is missing when documenting Tableau server without other data sources in doc, docx and pdf output formats
  • Incorrect format for SQL Server packages switch [/ssp] is present in the "Save as batch" window if no SSIS package from SQL Server is selected in the SSIS packages grid in Integration services tab
  • Missing information that the creation of database schema snapshot process has finished successfully
  • "Parse error: [Incorrect syntax near '.'] at [position: 2994, line: 68, column: 40]" error is encountered when generating database documentation in doc, docx and pdf output formats
  • SSIS packages from the SSISDB Catalog and SSIS project file are not shown in documentation when documenting them along with databases in doc, docx and pdf output formats
  • Two or more SSRS items from file system cannot be documented at the same time using the CLI switch [/rsff]
  • CLI error return code [1] for "general error" is shown when a database schema snapshot is successfully created through the CLI
  • Changes:
  • SSIS package "Design time properties" XML code is no longer generated inside of "Package properties" section in documentation

New in ApexSQL Doc 2017.04.0703 Patch (Jul 12, 2017)

  • Fixes:
  • SSIS control flow diagrams are not shown in documentation when documenting SSIS 2016 packages that contain CDATA section other than DesignTimePropertis in the package source
  • Changes:
  • SSIS package "Design time properies" XML code is no longer generated inside of "Package properties" section in documentation

New in ApexSQL Doc 2017.04.0702 Patch (Jul 12, 2017)

  • Fixes:
  • "Object refference is not set to an instance of an object" error message is shown when documenting SSAS 2016 Tabular databases in PDF output format
  • "Parse error: [Incorrect syntax near '.'] at [position: 2994, line: 68, column: 40]" error is encountered when generating database documentation in DOC, DOCX or PDF output format

New in ApexSQL Doc 2017.04.0701 Patch (Jul 4, 2017)

  • Fixes:
  • "Specified cast is not valid" warning message appears when trying to connect to SQL Server 2016 SSISDB catalog
  • "No data source is selected for documentation" information message appears when trying to document SSAS databases or SSRS items separately

New in ApexSQL Doc 2017.04.0695 (Jun 19, 2017)

  • Enhancements:
  • Support for Tableau server in chm and html output formats
  • CLI switches:
  • Include Tableau Server sites [/tss]
  • Exclude Tableau Server sites [/etss]
  • Include Tableau Online sites [/tos]
  • Include Tableau server details [/tsd]
  • Create database snapshot [/cdbsnp]
  • Include database snapshot [/dbsnp]
  • Database snapshot output directory [/dbsnpod]
  • Database snapshot file name [/dbsnpfn]
  • Fixes:
  • “Object reference is not set to an instance of an object” is encountered when documenting databases with customized object options for SQL tables
  • “Object reference is not set to an instance of an object” is encountered when a database schema snapshot is documented in chm and html output formats
  • Unhandled exception is encountered when removing a created database schema snapshot from the selection grid in the Database engine tab
  • Application stops responding when connecting to Tableau Server with credentials for Tableau Online
  • Unhandled exception is encountered when editing a column Description of a SQL stored procedure in the Extended property editor window
  • SQL tables are missing from documentation when documenting through the CLI and specifying the switch for including the “Permission” section for SQL tables in the documentation
  • Timeout expired and "A network-related or instance-specific error" message is encountered when documenting database schema snapshots in chm and html output formats
  • Saved selected database snapshots in the project file are not checked as selected when the project file is opened again
  • Settings from the Options window are not saved in the project file
  • Switching the extended property from one to another in the Extended property editor will reset the selection in the grid
  • SQL Server data type "nvarchar(-1)" is displayed in the doc, docx and pdf documentation instead of "nvarchar(max)" for SQL table column statistics
  • “Graphical dependencies” section remains open after clicking the “Collapse all” hyperlink in documentation in chm and html output formats
  • Wrong formatting of executed SQL tasks code in SSIS documentation
  • Wrong formatting of user variables code in SSIS documentation
  • Wrong formatting of connection managers code in SSIS documentation
  • The window minimize button in the documentation progress bar does not minimize the entire application
  • The progress bar appears under the Server objects tab when using the Community or Standard edition of the application
  • The “Search” button in the Extended property editor is not synchronized with the “Close” button in the “Search” section
  • Documentation can be created even when no data source is added or selected
  • The last used file path for adding a database snapshot is not remembered
  • When choosing the location to install application, there is no option to create a new folder
  • A second warning message “Connection to server failed. Make sure the server is running” is encountered when trying to connect to an inaccessible Tableau server
  • Tab stops are not configured properly for “Add Tableau server” window
  • “Delete intermediary files” checkbox can be selected by clicking on a blank space next to the same option button
  • “Document style” in Style tab in Defaults window can be selected by clicking on a blank space next to the same option button
  • “OK” and “Refresh” buttons are not available for a long time in Local tab in Servers browser when connecting to a new server
  • Defaults window tabs specific for the Standard and Professional editions of the application are available in the Community edition after closing the restriction message
  • Unselected options from the Site details tab are included in Tableau Online documentation in doc, docx and pdf output formats
  • Wrong object name and icon are displayed in the "Edit extended property" window in the Extended property editor
  • Added database schema snapshots are not shown in “Batch script” section in "Save as batch" window
  • Changes:
  • CLI switch Output format [/of] is now Output type [/ot]

New in ApexSQL Doc 2017.03.0674 Patch (May 23, 2017)

  • Fixes:
  • "Object reference is not set to an instance of an object" error is encountered when documenting databases with "Indexes" option deselected in the Table options section of the Database objects tab

New in ApexSQL Doc 2017.03.0669 (May 15, 2017)

  • Enhancements:
  • Database schema snapshots in doc, docx and pdf output formats
  • Support for Tableau server in doc, docx and pdf output formats
  • Fixes:
  • Missing informative message when there are no database schema snapshots selected in the Database engine tab and one of the Database engine sub-tabs are clicked
  • Customized copyright text is not documented when generating documentation through a batch file
  • Settings from the Options window are not saved in the application project file

New in ApexSQL Doc 2017.02.0642 (Apr 18, 2017)

  • Enhancements:
  • Database schema snapshots in chm and html output formats
  • Support for SQL Server vNext CTP1
  • Support for SQL Server Management Studio v17.0 RC3 integration
  • Fixes:
  • Null reference exception” error is encountered when documenting an empty SSAS tabular model database
  • SQL columns and SQL indexes documentation columns are misaligned when setting the Options presets slider to Detailed
  • SQL Server properties cannot be excluded from the generated documentation in chm, html, doc, docx and pdf output formats
  • SQL Server objects cannot be documented without SQL Server properties in chm, html, doc, docx and pdf output formats
  • Wrong key column is shown for SQL indexes documented in chm and html output formats
  • Table of contents nodes for SQL Server objects and properties are missing from documentation in doc, docx and pdf output formats
  • Could not find the part of the path” error is encountered if Illegal file naming characters are used in documentation output folder path when documenting SSAS tabular model databases in chm output format
  • Object reference not set to an instance of an object” error is encountered if Illegal file naming characters are used in documentation output folder path when documenting SSAS tabular model databases in docx, doc and pdf output formats
  • Description from columns is missing in SSAS tabular model database documentation in chm, html, doc, docx and pdf output formats
  • Data model diagrams are not generated in the database documentation when the “Additional attributes for tables and columns” option is enabled in the Database options tab
  • Auto update statistics description is wrong for SQL Server properties in documentation in chm and html output formats
  • Data model diagrams are being generated in the documentation even if the “Data model diagram” option in the Database options tab is disabled when the project is saved and used as a batch file
  • Additional attributes for tables and columns” option is not saved in the Database options tab in the Project defaults window
  • Dependency type” and “Dependency layout” options are not saved in the Database options tab in the Project defaults window
  • SQL views pages are missing from the documentation in chm and html output formats
  • Default output location is used instead of the user defined output location when generating documentation in html output format
  • SSIS packages passwords are visible in the Integration services tab
  • Connection timeout and Execution timeout options allow letter characters to be typed in the SQL Server Connection options window
  • When setting the Option presets to Fast only the “Show server node in .chm documentation” option is enabled in the Database options tab
  • This page can't be displayed” message appears in file system SSIS packages documentation in chm output format
  • Object filter is no longer applied after generating documentation in chm, html, doc, docx and pdf output formats
  • Documentation is generated containing all database objects when Contains and Ends with filter clauses are used in the database objects filter
  • Table of content nodes for SQL Server objects and properties are missing from documentation in doc and docx output formats
  • Wrong key column is shown for SQL indexes in documentation
  • Columns in documentation are misaligned for SQL indexes and SQL columns when the option presets are set to detailed
  • Changes:
  • Computed column details can now be excluded from documentation when the “Additional attributes for tables and columns” option is unchecked in the Database options tab
  • SQL Server objects can be documented without also having to document SQL Server properties

New in ApexSQL Doc 2017.01.0605 Patch (Mar 13, 2017)

  • Fixes:
  • Columns in documentation are misaligned for SQL indexes and SQL columns when the option presets are set to detailed
  • Changes:
  • SQL Server objects can be documented without also having to document SQL Server properties

New in ApexSQL Doc 2017.01.0599 (Mar 2, 2017)

  • Enhancements:
  • GUI themes:
  • Colorful
  • Dark
  • Fixes:
  • Object reference not set to an instance of an object” error is encountered when generating database documentation with unselected "Indexes" option in the Table options menu in the Database objects tab
  • Data flow and control flow diagrams are missing from the generated documentation for a SSIS 2012 package with non-English characters
  • Object reference not set to an instance of an object” error is encountered when documenting SSIS 2016 packages from the file system when only SSIS 2016 is installed
  • Data model diagrams are missing in documentation for SQL tables that contain a Data model diagram with dimensions larger than 2,432 x 39,474 pixels
  • Parse error: [Incorrect syntax near '@CONSECUTIVO'] at [position: 1286, line: 71, column: 37]” error is encountered when generating documentation for a SQL Server 2008 R2 database which contains the try_parse statement, in doc, docx and pdf output formats
  • SSIS packages cannot be added in Add integration service packages window from more than one default named Integration services instance
  • Half of the options in the Database options tab cannot be selected when navigating using keyboard controls
  • SQL table with unique index in database graphical dependency diagram is linked to a missing page in chm and html documentation
  • Changing the “Compile timeout” value in Options window doesn’t have any effect on the duration of chm documentation compilation
  • "AutoMapper.AutoMapperMappingException" error is encountered when documenting a SSAS multidimensional database with no measure group dimensions in chm and html output formats
  • Documenting SSIS packages from the SSIS 2012 package store or from the file system generates empty documentation in doc, docx and pdf output formats when only SSIS 2012 is installed
  • Code for SQL tasks is not formatted in SSIS package chm and html documentation output formats
  • Code for user variables is not formatted in SSIS package chm and html documentation output formats
  • Shift+Enter) shortcut cannot be used to skip to another row in the Comments textbox under the Output tab in the Options window
  • Option presets are not responding fluently to preset slider position changes
  • SQL code for XML schema collection is not clearly formatted in chm and html documentation output formats
  • No syntax highlighting for SQL code for documentation in doc, docx and pdf output formats
  • The Windows taskbar is not displayed when hovering mouse when the “Auto-hide the taskbar” option is checked and the application is maximized
  • Data model diagrams section expands when clicking the Collapse button in the Graphical dependencies section in chm and html documentation output formats
  • Table sections are not collapsing in the Data source views page of the SSAS multidimensional database documentation in chm and html output formats
  • Index columns section is not properly formatted in chm and html documentation output formats, when the "Explicitly document indexes" option is checked for SQL tables under the Database objects tab
  • SSRS items can’t be removed when the Delete keyboard button is pressed in the Add reporting services items window
  • The application cannot be integrated in SQL Server Management Studio 16.5.3
  • The “Extended properties” option under the Package details tab and the Database objects tab under the Defaults window is disabled when “Include extended properties” option is unchecked in Database options tab
  • Changes:
  • Sample values “Sample header text” for page header and “Sample footer text” for page footer are removed from the application Standard edition documentation
  • CLI return error code [3] for “invalid switch format” error is now [7]
  • CLI return error code [3] for “value out of range” error is now [8]

New in ApexSQL Doc 2016.05.0481 (Oct 27, 2016)

  • Enhancements:
  • Support for SSAS 2016 Tabular databases written in TMSL
  • Save project as batch file
  • Fixes:
  • Incomplete table in server configuration page in Azure database documentation
  • Wrong page linked for SSIS configuration settings in HTML documentation
  • Wrong page linked for SSIS configuration settings in CHM documentation
  • Broken links in CHM documentation for all table links under "Datatypes" section
  • The application does not document Schemas objects when chm is set as output
  • Documentation creation failed because the intermediary file path for SSIS cannot be found
  • Unable to execute file in temporary directory. Setup aborted, when downloading and installing application
  • The default output location is not saved in the project file
  • The documentation output format is not saved in the project file
  • Object filter settings not working right when selecting a few objects
  • SSAS Database details tab missing Project defaults
  • The "Filter" check boxes column is excessive in the "Database objects" tab
  • Missing scrollbar in SSAS documentation at MDX script page in Calculations
  • Shortening the title of reporting service item in generated DOC format
  • Analysis & add reporting services dialogs cannot be closed by ‘Esc’ key
  • SSRS documentation main page is not displayed at start
  • SSRS item details tab missing Project defaults
  • Missing shortcut for Add SSAS database option in Options menu
  • Missing shortcut for Add SSRS database option in Options menu
  • SSISDB documentation main page is not displayed at start
  • Bad documentation style in HTML format
  • Collapse image in SSRS documentation in html format
  • Data model diagram not generated for the table that does not have Primary key defined
  • Extended properties cannot be edited on a column level for specific database

New in ApexSQL Doc 2016.04.0425 (Sep 15, 2016)

  • Enhancements:
  • Export CLI help as HTML
  • Warning handling switch
  • 15 new return error codes:
  • Invalid value
  • Value out of range
  • Invalid file path
  • Invalid project file
  • Unsupported edition
  • Invalid activation key
  • Trial has expired
  • Connection timeout
  • Connection failed
  • IO error
  • Operation canceled
  • Application error
  • Execution error
  • Execution timeout
  • Insufficient permissions
  • Fixes:
  • Incomplete table in server configuration page in Azure database documentation
  • Output file formats remain locked as in community mode when application is activated
  • Scrolling the mouse wheel does not affect the scrollbars in Output options for Styles and Custom text forms
  • Parse error: Incorrect syntax near 'SELECT' is encountered when documenting a specific database
  • Metro style documentation saved in a project file is documented in a different style via CLI
  • Parse error: 'Cannot Recognize Token' is encountered when documenting specific database in docx format
  • The 'value' for parameter @StartDate is missing from SSRS documentation in Word/PDF format
  • Error is encountered when documenting SSISDB Catalog package with 'space' character in file name
  • Documentation of SSISDB catalog packages created empty in docx/pdf format on Windows 7
  • Parse error: [Cannot Recognize Token [ ] in [position: 5774, line: 196, column: 27]] at [position: 5774, line: 196, column: 27] in query [ype, Encoding, LocalParent, LocalChild, LockStatus, PendingCommand)
  • “Query” dropdown missing in a certain part of the SSRS documentation in chm/html format
  • Settings from SSIS project file missing when loading a ApexSQL Doc project file
  • When refresh button is clicked, all of the loaded SSAS databases disappear
  • “Query” dropdown missing in a certain part of the SSRS documentation Word/pdf format
  • SSRS items are grouped together with SSAS databases in .docx documentation
  • Wrong section title in SSRS documentation navigation pane
  • Missing information about usage format for /rsfn switch in CLI help
  • Missing information about usage format for /ersfn switch in CLI help
  • Missing information about usage format for /rsfs switch in CLI help
  • Missing information about usage format for /ersfs switch in CLI help
  • Empty SQL section in the documentation
  • Empty SQL query definition section displayed in SSAS documentation
  • Wrong error code and output in CLI when trying to connect remote server without valid credentials
  • Missing output for successfully completed operation in CLI
  • Wrong error code and output for invalid specified file path in CLI
  • Wrong error code and output for invalid specified project file in CLI
  • Wrong error code and output in CLI when application is used as Standard edition
  • Wrong error code and output in CLI when trial period has expired
  • Wrong error code and output in CLI when MSSQLSERVER service is paused or terminated
  • Wrong error code and output in CLI when operation is terminated by user
  • Changes:
  • New product icon

New in ApexSQL Doc 2016.03.0403 (Aug 2, 2016)

  • Enhancements:
  • SQL Server Management Studio 2016 integration
  • SQL Server Reporting Services documentation
  • Document SSIS packages from SSISDB catalog
  • Document SSIS packages from project files (.dtproj)
  • Document SSIS package details:
  • Project parameters
  • Log entry information
  • Extended properties
  • Configuration settings
  • SSIS source and destination mapping
  • Dependencies between SSIS packages and referenced database objects
  • Support for SSIS 2016
  • Fixes:
  • "Parse error: Incorrect syntax near '@vLogin'" error is encountered when documenting databases in doc, .docx and .pdf output formats
  • "Parse error: Incorrect syntax near 'int'“ error is encountered when documenting databases in doc, .docx and .pdf output formats
  • "Parse error: Incorrect syntax near 'AS'“ error is encountered when documenting specific database in doc, docx or pdf output formats
  • "Parse error: An object or column name is missing or empty“ error is encountered when documenting specific database in doc, docx or pdf output formats
  • "Application error: 'Exception in GetDataItemTableId'" error is encountered when documenting specific SSAS database
  • ApexSQL Defaults in SSIS package details tab does not work
  • ApexSQL Defaults doesn’t work for any Dependency options settings
  • "Parse error: Incorrect syntax near ','"
  • "Parse error: Incorrect syntax near 'SYSTEM_VERSIONING'"
  • "Parse error: Incorrect syntax near 'FOR'"
  • "Unhandled exception: 'Object reference not set to an instance of an object'" is encountered when documenting specific SSAS database
  • My defaults in Database details tab is not working correctly
  • “Parse error: Incorrect syntax near 'XML'” is encountered when documenting a specific SQL Server database in .pdf format
  • Settings for documenting Data model diagrams are not turned on by default
  • Missing switch for including Dictionary in Documentation
  • Unsupported file types can be included in Add integration services packages modal dialog
  • Sending Logs not working in SSMS addin
  • "System.NullReferenceException" is encountered when documenting SSIS packages when not having the required Integration services installed
  • Can't document a single package from the file system, via CLI
  • Unnecessary dialog pops up when clicking my defaults in SSAS database details
  • Can't document a single package from package store, via CLI
  • Can't document a single package from SQL Server, via CLI
  • "Parse error: Incorrect syntax near '('" is encountered when documenting master database from SQL Server 2014
  • Output options not accessible in certain situation when no datasource is added
  • "System.NullReferenceException" is encountered when connecting to two SSIS servers and selecting the Package details tab
  • "System.StackOverflowException" is encountered when documenting a specific database in Word/PDF formats
  • Error encountered when documenting SSIS packages from a project file in CLI or PowerShell
  • It is possible to generate documentation without any input
  • Documentation can be generated with empty SSISDB catalogue
  • Incorrect password error when documenting encrypted SSIS package with valid credentials in PDF format

New in ApexSQL Doc 2016.02.0357 (Apr 20, 2016)

  • ENHANCEMENTS:
  • SQL Server 2016 RC3 support
  • SQL Server Analysis Services documentation
  • Database model documentation
  • The following Azure SQL Database V12 object and properties are now fully supported:
  • Objects:
  • Assemblies
  • Asymmetric Keys
  • Certificates
  • Defaults
  • Encryption
  • Extended properties
  • Fulltext catalogs
  • Fulltext stoplists
  • Indexes
  • Partitions, partition functions, and partitions schemes
  • Rules
  • Search property lists
  • Sequences
  • Symmetric keys
  • XML schema collections
  • Enhancements in previously supported object types:
  • Indexes:
  • COLUMNSTORE indexes
  • Relational indexes:
  • PAD_INDEX
  • FILLFACTOR
  • SORT_IN_TEMPDB
  • ALLOW_ROW_LOCKS
  • ALLOW_PAGE_LOCKS
  • MAXDROP
  • DATA_COMPRESSION
  • Stored procedures:
  • WITH ENCRYPTION
  • FOR REPLICATION
  • EXTERNAL NAME
  • Tables:
  • ON keyword
  • TEXTIMAGE_ON
  • column_definition
  • NOT FOR REPLICATION
  • ROWGUIDCOL
  • column_constraint, computed_column_definition, table_constraint
  • FILLFACTOR
  • NOT FOR REPLICATION
  • index_option
  • PAD_INDEX
  • FILLFACTOR
  • ALLOW_ROW_LOCKS
  • ALLOW_PAGE_LOCKS
  • DATA_COMPRESSION
  • ON PARTITIONS
  • Triggers:
  • WITH ENCRYPTION
  • CLR-triggers
  • FOR REPLICATION
  • EXTERNAL NAME
  • User defined types:
  • CLR-types
  • ROWGUIDCOL
  • Users:
  • Database-contained users
  • Views:
  • WITH ENCRYPTION
  • FIXES:
  • "Parse error: Incorrect syntax near 'index'" error is encountered when documenting a database in Word format
  • SSIS diagrams are not documented when using Word or PDF output formats
  • Activation upgrade from Standard to Professional edition is disabled
  • Missing scroll bars in CHM output format
  • Project saved in evaluation of ApexSQL Doc cannot be loaded in Standard edition
  • Error when documenting SSIS store packages in Word/PDF “Could not find a part of the path 'C:\Users\User_name\AppData\Local\ApexSQL\ApexSQLDoc\Intermediary\Temp8048\SSIS\WIN-L9QH41R7LP9\package_index.htm'”
  • Parse error: [Incorrect syntax near 'ON'] error is encountered when documenting a Azure SQL Database V12 in Word/PDF format
  • Broken images in the Preview section under the "Styles" tab
  • Command line window appears every time while generating documentation and its maximized
  • CHANGES:
  • ApexSQL Doc “Developer version” is renamed to ApexSQL Doc “Standard edition”
  • Documenting integration services is now available only in ApexSQL Doc “Professional edition”

New in ApexSQL Doc 2016.01.0326 (Dec 12, 2015)

  • Enhancements:
  • SQL Server 2016 CTP3 support
  • SQL Server Management Studio 2016 CTP3 integration
  • Interactive graphical dependencies diagram
  • Granular documentation of object level attributes
  • Fixes:
  • Table options pane from the database object menu is cut on some display resolutions
  • SSIS diagrams won't be displayed in DOC or PDF output document if some specific options are unchecked in the "Package details" tab
  • The application causes SQL Server Management Studio to stop working when the add-in is not integrated
  • The same variables are documented for each task separately
  • "Some packages could not be loaded without valid credentials" error is encountered when documenting specific SSIS package
  • Scrolling in any application's tab is not available until any option is changed
  • Ctrl+A doesn’t select all checkboxes in Database objects
  • Selected extended property for the database will be documented even if the extended properties are excluded from the documenting process
  • The description column is not removed from the output document if the "Include extended properties" option is unchecked in the application options
  • The "TrackColumnsUpdatetedEnabled" item is not correctly specified in the output documentation
  • Documentation in PDF is not properly formatted
  • "System.OutOfMemoryException" error is encountered when documenting specific package
  • The "Document procedure/function result set" option is not synced with the "Recordset" function attribute
  • The application fails to include custom header/footer settings for doc, docx, and pdf output formats, when using the project file in the CLI
  • The "Shortcuts" tab is added under the "Options" form
  • The "Extended property editor" column filter becomes unusable after setting the filter and clicking the filter icon in the top row
  • The "DependencyViewerConsole" process does not stop when documenting a database in PDF format using the CLI
  • The "DependencyViewerConsole" process does not stop when documenting a database in CHM or HTML format using the CLI or GUI
  • The application fails to properly apply the chosen date format in the output document
  • "Input string was not in a correct format" error is encountered when documenting specific SSIS package
  • Column names are not displayed properly in the "Table statistics" section of the report in CHM and HTML format
  • The add in file for SQL Server Management Studio integration is created in the following location: C:\Program Files\ApexSQL\ApexSQLSourceControl2015
  • Obsolete example for deprecated HxS file format found in the Examples folder of the installation folder
  • The "Transact SQL syntax highlighting" option remains checked even if the "Data definition language (DDL) script" option is checked
  • The application does not format HTML tags in the extended properties
  • Specific columns cannot be excluded from the documentation
  • The installation wizard offers SQL Server Management Studio integration even if that version is uninstalled
  • The application is unable to document database without showing the Server node
  • A parsing error is encountered when documenting specific database for DOC/DOCX and PDF file formats
  • The add-in menu in SQL Server Management Studio is not consistent with other ApexSQL menus
  • SSIS diagrams cannot be excluded from the documenting process
  • The application can be installed even if the minimum system requirement is not met
  • The application's add-in is not alphabetically sorted in Object explorer
  • ApexSQL Doc does not generate graphical dependencies for database objects that have only outbound dependencies

New in ApexSQL Doc 2015.04.0315 (Sep 25, 2015)

  • Fixes:
  • The application does not document database objects, if the Cumulative update 7 for SQL Server 2012 Service Pack 2 is installed
  • A parsing error is encountered when documenting specific database for DOC/DOCX and PDF output file formats

New in ApexSQL Doc 2015.03.0312 (May 16, 2015)

  • Fixes:
  • "Unexpected error occurred. Method 'ApexSql.Doc.Properties.CliStrings.ExtendedPropertiesHelp' not found." error is encountered when running the "/?" switch in the CLI
  • SQL code won't be highlighted for the specific objects
  • "System.IndexOutOfRangeException" error is thrown by the "Remove" button inside the "Integration services" tab
  • The header/footer settings is not being used when generating PDF
  • "Property accessor 'Children' on object 'System.Int32' threw the following exception:'Object does not match target type.'" error is encountered when removing SSIS package source
  • The dependency viewer console process stays in the task manager, even after the command prompt window is closed
  • Specific object types are not shown in the output document
  • No images for dependencies are displayed in the report generated from CLI with appropriate switches used
  • The application fails to preview inter-database dependencies
  • Custom text will be wiped out after opening a project from previous version
  • The install wizard does not recognize version of running SQL Server management Studio and will not allow installation, even when the running version is unchecked for add-in integration
  • The "Document server properties" option fails to updated in the main form until the application restart
  • The logo will be removed if intermediary files are set to be deleted after documenting
  • Missing table icons inside document generated from CLI
  • Columns width is not properly determined in the generated documentation
  • The "Use short names" tooltip does not show up in application Deafults, if the option is not enabled
  • The application is installed successfully even both SQL Server Management Studio (2012 and 2014) are running
  • "Parameter is not valid." error is encountered when documenting SSIS package whose diagram position exceeds the limit of 65k pixels
  • The application help is not redirected to knowledge base content
  • The application adds excessive lines in SQL script for tables when the "Include DDL script" option is checked
  • "Parse error: [Incorrect syntax near 'TRANSACTION']" error is thrown when documenting database from SQL Server 2005
  • Date format change inside options is accepted only after application restart
  • Documenting database from SSMS 2014 will display incorrect tab labels in application
  • Saved projects from previous applications major versions cannot be opened
  • "The given key was not present in the dictionary." error is encountered when documenting SSIS package in PDF/DOC/DOCX format
  • The image placeholder will be inserted automatically, and documented as a broken image when using the application on x86 OS and SQL Server 2005 x86 installed
  • All icons in dependency type/layout drop menus are same

New in ApexSQL Doc 2015.01.0290 (Jan 5, 2015)

  • Enhancements:
  • The application now supports documenting of Control flow diagrams
  • The application now supports documenting of Data flow diagrams
  • Documenting process is now up to 50% faster for all output formats
  • Graphical dependencies documenting is now up to 23% faster, depending on the output format
  • Display page numbers in .doc/.docx/.pdf documentation
  • Choose either to name graphical dependencies with schema qualification or server
  • Fixes:
  • The "Include table of contents in .doc and .docx formats" option is incomplete
  • Diagrams for packages are missing when path for Intermediary files is changed
  • Filter for Roles shows each role twice
  • The "Include table of contents in .doc and .docx formats" option cannot be changed in the application defaults
  • The "One or more errors occurred." error is encountered when documenting database from Azure
  • Incorrect image for Messagetype objects in the Extended property editor grid
  • Incorrect and inconsistent message during the installation, if the application is already running
  • The "Pivot" icon in the Data Flow diagram is not properly documented
  • The "Merge Join" icon is not properly documented
  • The "Flat File Destination" icon fails to appear in the output document
  • The Connection Managers section in the main report pane indicates that "No item exists", even it is clearly visible after expanding the three in left pane that these actually exists in the package
  • The application fails to generate Data Flow diagram for teh particular SSIS package
  • The "Index was outside the bounds of the array." error is encountered when documentng specific package
  • The control flow diagram is not properly created for the particular object
  • The temporary images used to document graphical dependencies will be created in the destination path instead in the intermediary folder
  • The background color is inconsistent for all color in the Custom text tab - "Preview" section
  • The "Data at the root level is invalid. Line 1, position 1." error is encountered when documenting specific package
  • The application fails to initiate from SQL Server Management Studio Object Explorer
  • Extended property editor cannot be used on databases with more than 20,000 objects
  • Deselecting some columns in 'Select Column Option' results that grid with remaining columns doesn't populate all space left
  • Incorrect preview for the specific characters in the "Preview" section of the "File name" template
  • The "Save changes to the project" dialog appears even if there is no changes made in the project
  • Excessive scroll bar inside the "Preview" pane, from the "Custom text" tab
  • The date tag is not previewing in the "Preview" section of the "File name" template settings in the "Naming" tab
  • The application is installed in a separate folder in the Start menu
  • The "Preview" section fails to appear when the application is started
  • The background color is inconsistent for all color in the Custom text tab - "Preview" section
  • Specific databases cannot be documented in html, doc, docx and pdf with graphical dependencies included
  • The header and footer text in the Custom text tab are formatted as Bold, Italic and Underline by default
  • Wrong number for the maximum characters allowed is specified in the "Creating the documentation has failed" window
  • The "Explicitly parse database for improved dependency accuracy" option needs to be disabled/grayed when the "Include dependency list/tables" option is unchecked
  • The "Include data definition language (DDL) script" option keyboard shortcut does not work
  • The date tag is not previewing in the "Preview" section of the "Documentation title" template settings in the "Naming" tab
  • Date format field in output options should be pre-defined drop down pick list
  • The state of the buttons in the "Custom text" tab is not recognized
  • Initiating the "Defaults" button, switches the image position to "None", instead completely removing image path
  • Missing "Name" column in the documentation when documenting SSIS packages in DOC, DOCX, and PDF
  • The connection password is not saved even if the "Remember password" is checked
  • The "/ps" and "/po" switches can be specified for the chm or html documenting even if this is senseless
  • The image inserted in header/footer is broken in the output chm document when the intermediary files location is not set to default
  • The row filter in the "Extended property editor" window is case sensitive
  • The "Extended property editor" window will close on ESC key without any warning message
  • The application can be uninstalled without warning if SQL Server Management Studio is still running
  • Missing switches for the new options in the "Custom text" tab
  • The application fails to format HTML tags in the extended properties
  • The "Parse error: Parse error: Error : [Incorrect syntax near 'AS']" error is encountered when documenting specific database in doc, docx or pdf
  • The application fails to generate documentation in the HTML output format

New in ApexSQL Doc 2014.03.0277 (Nov 3, 2014)

  • Enhancements:
  • The application now integrates as an add-in in SQL Server Management Studio 2014/2012
  • An option to add images in header/footer of the output document is added for CHM and HTML output formats
  • An option to choose a page orientation (portrait or landscape) of the output document is added for DOC, DOCX, and PDF output formats
  • An option to select the page format (A3 or A4) of the output document is added for DOC, DOCX, and PDF output formats
  • Options to edit header/footer text, font, formatting, and color are added
  • An option to select the dependency level for object dependencies is added
  • An option to include/exclude extended properties on the object type level is added
  • Graphical dependencies documenting is now up to 24% faster, depending on the output format
  • Fixes:
  • The "/f" switch does not work
  • The project file is processed incorrectly, when opened with a double click
  • The application fails to create graphical dependencies for the first database, when two or more databases are included in the processing
  • The application cannot document Windows Azure SQL Databases in CLI
  • The application hangs when the switches are duplicated
  • The "/?" switch does not work in the CLI
  • The "The given key was not present in the dictionary." error is encountered when canceling the documenting process
  • The application fails to document graphical dependencies for objects with 100 and more parent/children objects
  • The documentation fails if the ".gif" icon is renamed in the application install directory
  • Intermediary files are not deleted, and the dependency viewer process remains active, when canceling the documenting process
  • The "Scale" option in the "Dependencies" tab does not work
  • The documenting process hangs for hours on a specific database function
  • The "Collapsible image" is displayed instead of "+" sign in some parts of the documentation
  • The "System.Argument exception Parameter is not valid" error is encountered when starting another instance of the application, while one instance is still running
  • Inconsistent list of the available tags in the Custom text tab, and in the application "Default" settings
  • The "/srd:n" switch will not exclude the "Server info" node from the documentation
  • SQL Server login status is not documented when using doc, docx, or pdf as an output format
  • The dropdown menu of grid filtering in the "Extended property editor" window does not offer reselection
  • The "System.IndexOutOfRange exception" is encountered when documenting database information on specific databases
  • Documenting process hangs when documenting specific database
  • Generating documentation failed if the already existing folder is specified using the /od switch in the CLI, when using the HTML output format
  • Documentation dictionary is not sorted in alphabetical order in specific situations
  • The "Destination patch check" message pops up when documentation is created from CLI

New in ApexSQL Doc 2014.02.0265 (Jul 30, 2014)

  • Enhancements:
  • The application now fully supports Windows SQL Azure Databases
  • The application now supports PDF output format
  • The application now supports new metro style for the generated documentation
  • Fixes:
  • The application cannot detect SQL Server 2005 version when installed on the x64 bit Windows Server 2003 operating system
  • Incorrect name of the application log files
  • Local servers cannot be removed from the drop down list in the 'Add SQL Server' window
  • The "Custom text" changes every time when clicking on the "Defaults" options
  • The "Send logs" functionality is incomplete when a mail client is not present in the system, and after the first attempt every press on the "Send logs" option will not work while causing the application window flashing
  • When the "Use filter" check box is set manually, it will stay checked even after pressing the "Uncheck all" check box
  • Unchecking the "Make sections collapsible" option will not remove the warning message related to the JavaScript from the "Preview" section
  • The "Full preview is not available with JavaScript turned off." message in the "Styles" option is misguiding and wrong
  • When checking the "Server objects" and the "Database objects" check box for the Object type, the associated Use filter check box will be checked automatically as well
  • The incorrect version of the application is shown in the Control Panel after the application is updated to a newest version
  • The "MaximumDegreeOfParallelism" in the Table properties section of the final document displays a negative value
  • The "Graphical dependencies" are excluded from the report for the objects which do not have any dependent child objects even if the "Parents and descendants" option is set
  • Visible legacy windows when activating the application
  • After updating to a newest version an old icon is displayed on the desktop
  • Incorrect link to the product page in the Support section in the Resource tab
  • The "Sample preview" in the "Output" option preview is missing
  • The "Collapse all" option in a documentation is not working in the Google Chrome browser
  • Incorrect tooltips are used for options
  • Inconsistency between icons in the main GUI
  • Incorrect name of the 'Database description' in the 'Extended property editor' window
  • Incorrect clickable area for the "Server objects" option
  • An option to resize or scroll window in the "Project defaults" window is missing
  • Incorrect GUI changes when the "Table options" option is selected
  • The "Granular filter" editor drop down menu for selecting the name or schema is always empty
  • The “Could not connect to SSIS " message will popup when the user wants to connect to SQL Server for documenting the SSIS package
  • The "Database engine" option submenus should not be disabled until a datasource is selected
  • Incorrect details in a documented documentation for the "Current Compatibility Level" option
  • Some Latin characters are replaced with Chinese logograms when application is installed and used with the Chinese version of Windows OS
  • The application cannot document databases from a local server after trying to connect on a Windows Azure SQL Database
  • The Table of Contents does not exist in the .doc and the .docx format
  • The "System.OutOfMemoryException" error is encountered when trying to edit a database with ~10,000 procedures in the "Extended property editor" window
  • The "System.OutOfMemoryException" error is encountered when documenting databases with a large number of stored procedures
  • The filetable information is missing in the doc/docx file format
  • The "The documentation can be incomplete" warning message is shown while compiling a document for a database with the unicode characters
  • The "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding" warning message is displayed after the application is hanging for 20 min in the Documenting state
  • The "Incorrect syntax near 'DDL_DATABASE_SECURITY_EVENTS'" error is encountered when documenting a database containing both the application and the database roles to the doc/docx formats
  • The "An entry with the same key already exists" error is encountered when documenting SQL Server 2000 database to the doc/docx file format
  • The "The surrogate pair (0xD952, 0xD952) is invalid." error is encountered when processing a database in the doc/docx file format
  • The "An entry already exists" error is encountered when documenting a specific database
  • The application is not releasing the RAM memory used for documenting after the documenting process is finished
  • There is no information in a generated documentation to the status of a created SQL Server login
  • The "Property cannot be updated or deleted" error is encountered when changing description for the Primary key objects
  • The "Destination patch check" dialog pops up every time when a documentation is created in the CLI
  • The "Permission to access the server" option in a created documentation is showing incorrect information for a SQL Server login
  • When refreshing the "Preview" option in the "Custom text" tab all text will be deleted
  • The "An exception occurred. The string was not recognized as a valid DateTime. An unknown word starting at index 0." error is encountered when generating documentation using the European date format
  • The "Parse Error: incorrect syntax near 'is'" error is encountered when the documentation is generated using the European date format
  • The "Object invalid. Extended properties are not permitted on 'dbo.', or the object does not exist" error is encountered when saving description in the "Extended property editor" dialog
  • Wrong spelling of the "List of stored procedures" subtitle of the stored procedure's "See also" section in the generated CHM documentation
  • Word wrapping in the documented .chm and .html file formats is not working
  • The "Extended property editor" window is not resizable and cannot be minimized or maximized
  • Changes:
  • The application has been split into three versions - Community, Developer and Professional

New in ApexSQL Doc 2014.01.0253 (Jun 24, 2014)

  • Enhancements:
  • The application now fully supports SQL Server 2014
  • The application now fully supports SQL Server Integration Services 2014
  • The application is now compatible with Windows 64-bit operating systems
  • Fixes:
  • The “Project defaults” option is not saving options for the entire application
  • Missing tooltip description after the “Bitwise set” option
  • The “Connection managers” section in the main report pane indicates that "No item exists", even it is clearly visible after expanding the three in the left pane that these items exist in the package
  • The "System.NullReferenceException: Object reference not set to an instance of an object" error is encountered when documenting SQL Server Integration Service packages from the file system
  • The application cannot flush the RAM memory used during the documentation process after the documenting process is finished
  • The “Trial expired” warning can be avoided if already existing application project is opened
  • The “System.IO.IOException” error is encountered when using HTML as output file type
  • Clicking the first checked check box will uncheck all others check boxes for the server and database objects
  • The “Dependencies” tab from the “Project Defaults” option has a spelling mistake - "Dependecies"
  • The “Cancel” button from the “Output” dialog does not work when the date format is marked as invalid
  • The “About” form includes incorrect copyright year information
  • The “Date format” sample preview in the “Options” dialog is not shown when any value is inserted
  • Missing information box with an explanation of available data format entry in the “Options” dialog
  • The “Output” dialog titles are half-visible
  • The “Refresh” button clears preview area from the "Styles" tab
  • The “Ctrl + A” keyboard shortcut does not work for the “Comments” field in the “Options” dialog
  • The “Index was outside the bounds of the array” error is encountered when documenting specific database
  • The "Could not connect to SSIS Package Store" error is encountered when trying to connect to Integration services
  • The “Extended property editor” feature can be accessible after the initial trial period is expired
  • Temporary folders are not deleted automatically when documenting to html format
  • The "Styles" option preview does not utilize the user data from the “Options” dialog
  • The application hangs in documenting state with the “Include system objects” option selected and doc/docx output file type is chosen
  • The “Object reference not set to an instance of an object.” error is encountered and process is terminated in case the database with reference to missed objects is documented in any of doc/docx formats
  • The “An object or column name is missing or empty.” parse error is encountered when documenting specific database
  • Documenting in .docx format is not possible on SQL Server 2012 for the specific databases
  • The “Out of memory” error is encountered after generating the documentation for the database which contains Unicode characters
  • The "Out of memory" error is encountered when documenting result exceeds 4000 pages in .docx format
  • The “Out of memory” error is encountered when creating the documentation for multiple large databases at once
  • Database with Unicode characters in the name cannot be documented in CHM format
  • The "Out Of Memory" error is encountered when documenting large database from remote SQL Server in doc/docx format
  • MS Office 2010 warns about unsecure contents and blocks editing of generated .doc file
  • The "At least one package should be specified" error is encountered when documenting Integration Service packages from various sources
  • Superfluous [] characters in the “Event notification” title
  • The “Warnings: Some packages cannot be loaded in whole or in part without valid credentials” error is encountered when documenting SQL Server Integration Services package(s) 2012
  • The “Craniate ERM Diagram ‘Component Licensing’” error is encountered when the “Graphical dependencies” option are selected
  • Changes:
  • New user interface that follows Metro UI style
  • The application now requires Microsoft .NET framework 4.0
  • Windows XP is no longer supported

New in ApexSQL Doc 2013.01.0238 (Oct 1, 2013)

  • Fixes:
  • The "System.IO.FileNotFoundException" error is encountered when creating a new project if .NET Framework 4.0 is installed in the system

New in ApexSQL Doc 2013.01.0237 (Jun 13, 2013)

  • Enhancements:
  • A tool-tip has been added to the “Date format” option in the “File output” section of the “Output” tab of the “Options” dialog in order to clarify that time can be formatted using the “Date format” option as well as to stress that the date format is case sensitive
  • Fixes:
  • The "Some packages cannot be loaded wholly or in part without valid credential" message is displayed shown when attempting to document SSIS packages
  • The “NotEnoughRightsException” error is encountered when attempting to document a database and the login used to authenticate to the SQL instance where the database resides isn’t a member of the db_owner or sysadmin SQL roles
  • The "The program encountered a problem. We are sorry for the inconvenience" error is encountered when attempting to document SSIS packages
  • The application log files aren’t created
  • The encrypted packages cannot be fully loaded even when using valid credentials
  • The CHM file topics containing SQL objects’ documentation are sorted incorrectly in the Content tab of the generated CHM document
  • The SQL objects listed in the “Objects that depend on” section of the documentation are sorted differently in DOCX and CHM generated documentation
  • Encrypted objects are missing from the generated DOC and DOCX documentation
  • The “Statistics structure and age” section is missing from the generated DOCX documentation
  • The columns listed in the “Datatypes” section of the generated DOCX documentation are sorted in a descending instead of an ascending order
  • An incorrect icon is used for SQL Server role objects in the generated DOC and DOCX documentation
  • SQL sequences are documented differently in the generated DOC and DOCX documentation and the entire “Sequence properties” section is missing from them
  • Links to the “Backup devices”, “Server roles” and “Server info” sections of the generated DOC and DOCX documentation are missing from the “See also” section
  • The values for the owner and creation date properties of SQL search property lists are missing from the generated DOC documentation
  • An incorrect value is shown for the type property of SQL jobs in the “Job properties section” of the generated DOCX documentation if the target SQL instance of the documented SQL jobs is unavailable
  • The application becomes non-responsive while documenting SQL stoplists
  • The name of the SQL instance saved in the project persists in the “SQL Servers” list located on the “Select databases for documenting” page, although a different SQL Server has been selected
  • The text in text fields in the “File format”, “Styles” and “Naming” pages of the “Output options” section of the project dialog cannot be selected using triple-click or the Ctrl+A keyboard shortcut
  • The “Add” button on the “Add integration service packages” dialog is not fully visible
  • Graphical dependencies for SQL sequences are missing from the CHM documentation created using the CLI
  • The uninstallation process can be started while the application is still running resulting in an incomplete uninstallation
  • The tooltip for the “Extended properties” icon in the Main grid is missing
  • The “Close project”, “Save” and “Save project as” options don’t appear in the Quick access toolbar until a project is opened
  • The text in the error “Unknown error has occur” is spelled incorrectly
  • Only the major version of the application is shown in the Version column of the Add/Remove programs in the Windows Control Panel
  • If only SQL services are to be documented, information about the related SQL queue and SQL contract is missing from the generated Help 2.x documentation
  • The non-default color scheme is not applied to the left menu
  • The icons used to represent the commands for adding database engines in the menu and on the “Select databases for documenting” page are different
  • The number of selected databases and packages is not updated in the application’s status bar when packages and databases are checked using the Space bar
  • The “Edit” button in the “Select packages for documenting” page is enabled even if no packages are selected
  • The values for “Data space in use and reserved for use”, “Index space and usage”, and “Allocated and unused space”, in the “Database information section” are different in the generated DOCX and CHM documentation for the same database; the values for “Containment”, “File stream non-transacted access level” and “File stream directory name” are missing from the generated DOCX documentation
  • The text in the message “Some packages cannot be loaded in wholly or in part without valid credentials”, which appears when attempting to document unsupported SSIS packages, is spelled incorrectly
  • The title of the “Recent projects” item located in the Quick access list is spelled incorrectly
  • The items “Create a new project”, “Open existing project” and “Save project as… ” located in the Quick access list don’t have tool-tips
  • The title of the topics documenting schemas in the generated DOCX and CHM documentation are different
  • The options located under the “DDL options” and “Miscellaneous” sections of the “Performance intensive options” page are not visible if the application window is at minimal window height
  • The link to the “Server index” section of the generated CHM and Help 2.x documentation is missing from the “About this documentation” section
  • The “Compilation error” error is encountered when generating Help 2.x documentation for SQL Server Integration Services Packages
  • Objects cannot be selected or deselected using the Space bar in the “Object filter grid”
  • The wrong SQL Server version (2011 instead of 2012) is shown in the “Object index” title of the “Objects by type” documentation topic
  • SQL Columnstore indexes are not documented correctly in the generated CHM documentation
  • The “Save changes dialog” is shown when closing a project immediately after it was opened, although no changes have been made
  • The size of the SQL stored procedure parameters is documented incorrectly
  • The “Description” section for primary keys is missing from the generated CHM documentation

New in ApexSQL Doc 2012.01.0235 (Jan 25, 2013)

  • Fixes:
  • The “Parse error: [Incorrect syntax near 'DESC']” error is encountered when documenting a database with non-clustered indexes containing an INCLUDE clause
  • The dependency graph only shows the SQL objects selected for documentation and the SQL objects which depend directly on them

New in ApexSQL Doc 2012.01.0234 (Dec 28, 2012)

  • 'Parse error: incorrect syntax' error is shown and the process is terminated when documenting a database which contains objects with Unicode characters in their names

New in ApexSQL Doc 2011.01.0229 (Dec 30, 2011)

  • Enhancements:
  • SQL Server Denali/2012 CTP3 databases can now be documented
  • Application now documents the following new SQL Server Denali/2012 object types:
  • Sequences
  • Search Property Lists
  • File Tables
  • Tooltips have been implemented for all output options
  • Graphical dependencies have been improved to include the following object types:
  • Users
  • Rules
  • Schemas
  • Asymmetric Keys
  • Symmetric Keys
  • Certificates
  • Fulltext Stoplists
  • Dependencies are now identified with higher accuracy when 'Explicitly parse database for improved dependency accuracy' option is OFF
  • Additional columns have been introduced for Table indexes in ‘Compiled HTML Help file (.chm)’: 'Description' and 'Size KB'
  • The following new switches have been added to CLI:
  • seo [/sequence_options] – Specifies Sequence documenting options
  • splo [/search_property_list_options] – Specifies Search Property List documenting options
  • Fixes:
  • Hyperlinks to excluded or non-existing and hidden object types may be created in ‘See also’ sections in ‘Compiled HTML Help file (.chm)’ format
  • Extra columns may be added to nonclustered index DDLs when 'Explicitly parse database for improved dependency accuracy' option is ON
  • Server Info’ hyperlink is created in ‘See also’ sections in ‘Compiled HTML Help file (.chm)’ format when ‘Document server properties’ option is OFF
  • System Services are documented when 'Include system objects' option is OFF
  • Server objects are documented in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats when 'Document server properties' option is OFF
  • Database Overview’ hyperlink is created in ‘See also’ sections in ‘Compiled HTML Help file (.chm)’ format when 'Include database summary information' option is OFF
  • Application roles are not shown in database object filter
  • Filtered out objects remain unchecked on database object filter after the respective filter is removed
  • Empty filters can be created for server and database objects on respective object filters
  • Check All' command may check not all objects on server object filter depending on the invocation
  • Unchecked objects become checked when cancelling changes to an existing filter on database object filter
  • Fulltext Stoplist selection is not saved into a newly created project the 1st time it is saved
  • Objects cannot be checked/unchecked with on database object filter
  • Progress is not reported in CLI when documenting in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Progress is reported incorrectly when documenting in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • objectname} custom text tag expands to full path for SSIS packages when documenting in ‘Compiled HTML Help file (.chm)’ format
  • Last opened project is not opened at start up when 'Show last opened project' is selected as startup action
  • Startup action changes from 'Show last opened project' to 'None' after an existing project is opened
  • Maximum Length’ property value is documented doubled for NCHAR and NVARCHAR-based User Defined Data Types
  • Database status is always documented as 'Unknown'
  • Column Level Dependencies’ section is missing for Triggers in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Triggers’ section is missing for Tables in ‘Compiled HTML Help file (.chm)’ format
  • Index Statistics Structure and Age' section is always empty in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Objects that depends on' section is not alpha ordered for Triggers in ‘Compiled HTML Help file (.chm)’ format
  • Change Tracking' property value is documented as 'A' vs 'AUTO' for fulltext indexes in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Index Columns’ section is missing for fulltext indexes in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Specified cast is not valid” error is encountered when documenting SQL Server 2000 database in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats with 'Statistical data analysis' option ON
  • An extension is always appended to the output file name in CLI when documenting in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Date format is not applied to generated documentation in ‘Word document 97-2003 (.doc)’ and ‘Word document 2007 (.docx)’ formats
  • Description' and 'Size KB' columns are missing from ‘Indexes’ section for Tables in ‘Compiled HTML Help file (.chm)’ format
  • Index names with unallowed characters are not enclosed in brackets in page titles
  • Table names with unallowed characters are not enclosed in brackets in ‘See also’ sections
  • Precedence Constraints’ section generated for SSIS packages is not alpha ordered
  • System.ComponentModel.Win32Exception exception is encountered when documenting more than 100 SSIS packages simultaneously
  • Unworkable hyperlinks to User Defined Data Types are created for Defaults in ‘Help 2.x file (.hxs)’ format
  • Empty document is created in CLI if output file name is specified with ‘.chm’ extension
  • Application doesn't prompt to save changes in the currently opened project when creating a new one after documentation in ‘Word document 97-2003 (.doc)’ or ‘Word document 2007 (.docx)’ format has been generated
  • Application doesn't prompt to save changes in the currently opened project when creating a new one if it has been modified
  • Creation date is put without time in generated documentation in ‘Compiled HTML Help file (.chm)’ format
  • Line breaks are not inserted in user comments in generated documentation in ‘Compiled HTML Help file (.chm)’ format
  • Copyright hyperlink does not open in generated documentation when specified without the "http://" prefix
  • Custom text tags may be either expanded incorrectly or partly ignored depending on the combination

New in ApexSQL Doc 2010.01.0228 (Apr 13, 2011)

  • Enhancements:
  • Application now supports 2 new output formats:
  • Word document 97-2003 (.doc)
  • Word document 2007 (.docx)
  • Encrypted SQL Server 2005/2008 objects can now be decrypted and documented (requires membership in the sysadmin server role)
  • Fulltext Stoplists can now be documented
  • SSIS Packages resided in SQL Server 2008R2 can now be documented
  • Extended properties on databases are now get documented
  • New VS 2010 style is now available for HTML-based output formats and set by default in all new projects
  • Custom text edit boxes now offer HTML syntax highlighting and auto completion of HTML tags
  • New Office 2007 style interface with ribbon bar, quick access toolbar, and ApexSQL Doc button has been introduced
  • New Resources ribbon bar has been introduced for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, Contact and Get Updates dialog boxes
  • New standard Project Management dialog has been introduced
  • Project Management dialog now shows recently used projects or projects stored in any folder of choice
  • Projects can be Pinned/Un-Pined to Recent Projects list on Project Management dialog
  • Project description can be edited directly from Project Management dialog
  • 'Show on Startup' option has been added to Project Management dialog box
  • - Startup Action options group has been added to Options dialog to control Project Management dialog behavior. Available choices are 'Show Project Management dialog', 'Show last opened project' and 'None'
  • Project Defaults can now be defined for newly created projects
  • Project options can now be saved as current user defaults settings
  • Project options can now be reset either to current user or to ApexSQL defaults
  • Each project option has now an associated tooltip with description
  • New Object Filter Editor allows to filter objects based on 'Exclude if' or 'Include if' conditions
  • New Object Filter Editor can use the following comparison operators: 'Equal', 'Not Equal', 'Between', 'Not between', 'Contains', 'Not contains', 'Begins with', 'Ends with', 'Any of' and 'None of' and the following logical operators: 'And', 'And not', 'Or' and 'Or not'
  • Main window status bar has been redesigned and now shows numbers of selected databases and SSIS packages and output format
  • New tooltip balloons have been added to data source bars of main window status bar
  • Options dialog has been redesigned with new Office 2007 button bar
  • Application can now be presented in 3 color schemes: Blue, Silver and Black
  • The following connection options have been added to Add/Edit SQL Server dialog: 'Execution timeout' and 'Encrypt connection'
  • The following new switches have been added to CLI:
  • /fso [/ft_stoplist_options] - Specifies Fulltext Stoplist documenting options
  • Fixes:
  • System.OutOfMemoryException exception is encountered when editing extended properties of a database with more than 10,000 objects
  • System.OutOfMemoryException exception is encountered when documenting databases with more than 10,000 objects
  • Crainiate.ERM4.Layouts.GraphException exception is encountered when cancelling documenting if ‘Graphical Dependencies’ option is ON
  • Objects are not alphabetically ordered in the 'Objects that depend on' section of User Defined Data Types
  • Package source doesn’t get documented for packages located in SSIS Package Store 2008 or SQL Server 2008
  • Maintenance plan SSIS packages located in SSIS Package Store 2008 don’t get documented
  • ‘Run As’ Job step property is always empty in generated documentation
  • DDL Triggers don’t have ‘Graphical Dependencies’ section
  • SSIS Package Store 2005 and 2008 cannot be documented simultaneously if they have the same name
  • Carriage returns are not preserved when documenting SQL Statement Source property of SSIS package
  • Non-schema bound objects get shown under 'Objects By Schema' node in table of contents of generated documentation
  • Documentation generated with ‘Show Nodes for Object Types that don’t Exist in Documented Database’ option ON contains links to non-existing object types in ‘See Also’ sections
  • Ctrl+C doesn't terminate ApexSQLDoc.exe process in CLI
  • 'Relationship' sub-node doesn’t get shown under Table nodes under ‘Objects By Schema’ node in table of contents of generated documentation
  • For documenting databases from CLI membership in the db_owner database role is required
  • PAGE LOCK and ROW LOCK attributes of Primary Keys aren’t shown as part of DDLs in ‘SQL’ section in generated documentation
  • Table referenced in ENABLE TRIGGER statement in stored procedure isn’t shown in 'Objects that depend on' section in generated documentation
  • Table referenced in DROP STATISTICS statement in stored procedure isn’t shown in ‘Objects that depend on’ section in generated documentation
  • Changes:
  • Copyright settings have been moved to Application options
  • Default Intermediary Files Location has been changed to \Users\\AppData\Local\ApexSQL\ApexSQLDoc2010\Intermediary
  • Regular Help button has been replaced with question mark button in title bar on all dialogs and windows
  • Custom Tags Converter has been removed
  • ‘Document Only Checked Databases’ and ‘Document All Databases Except Checked’ options have been removed
  • The following deprecated CLI switches have been removed:
  • /s [/server],
  • /d [/database],
  • /u [/user],
  • /p [/password],
  • Known limitations:
  • Extended property editor cannot be used on databases with more than 20,000 objects
  • Documenting stored procedures that indirectly/through another stored procedure or function call replication system stored procedures with ‘Include Documentation of Procedure/Function Result Sets’ option ON may result in replication jobs not functioning properly.

New in ApexSQL Doc 2008.08.226 (Oct 9, 2009)

  • Enhancements:
  • - The following CLI switches now accept IP addresses (surrounded with square brackets) in addition to data source names: /server, /database_engines, /integration_service_packages, /sql_server_packages
  • - Modules section of assembly documentation now show assembly methods along with where they're usage
  • Fixes:
  • System.OutOfMemoryException exception is thrown when documenting large databases (thousands of objects)
  • UserBreakedProcessException exception is thrown on attempt to save project after documentation process is cancelled
  • Variables in SSIS packages are not documented
  • Toolbar contents disappear after pressing Reset button in the Customize (toolbar) dialog
  • Public server role is not shown on Object Filter step nor is it documented
  • SsisPackageComparisonEngineException is thrown on attempt to document SSIS packages without Integration Services 2005 installed locally
  • Deleted SSIS package is recognized as Password Protected on Package Selection pane
  • /exclude_integration_services_packages CLI switch does not exclude specified SSIS packages from the documentation
  • /integration_services_packages CLI switch does not allow to document several packages at once
  • System.FormatException exception is thrown when documenting SSIS package with a single Data Flow Task
  • "Account is not db_owner for selected database" warning message appears twice when applicable for each database selected for documenting
  • "Critical error occurred when loading database metadata" error is thrown on attempt to document database under not db_owner account
  • It's impossible to connect to SSIS Package Store of locally installed Integration Services 2008
  • Reference to non-existing foreign key is shown as a link in table documentation
  • "Deprecated switch" message is displayed when a wrong value is specified for /server_object_types CLI switch (wrong message)
  • Objects get deselected on Object Filter step after selection profile export
  • Application does not remember location of last saved project
  • Application does not allow entering password for password protected SSIS packages
  • Servers are not sorted properly in SQL Server connection dialog shown for Integration Services
  • Users do not appear as Login references in generated documentation
  • Link to the user-defined datatype used in procedure parameters goes to non-existing page when documentation is made in HTML format
  • Embedded CrLf is not documented for Execute SQL Task item of SSIS packages affecting overall look of SQL statements contained in this source
  • Only first dependencies level is shown for views and procedures in graphical dependencies diagrams
  • SQL Server alerts in French language are not documented
  • Application documents dependencies on built-in SQL Server functions (it shouldn't)
  • Changes:
  • "SSIS Package Store" package location is now divided into "SSIS Package Store (SQL Server 2005)" and "SSIS Package Store (SQL Server 2008)"
  • /integration_services_packages CLI switch format was changed to service1[:SQL2005|SQL2008].package1.package2...packageN[:password]