ApexSQL Source Control patch release notes

Fixes:

• 203664: Database changes are not shown in the Action center tab after the linking process is done for databases containing objects with the With result sets command in a script
• 204017: Database changes are not shown in the Action center tab after the linking process is done for databases containing values inside quotes as a part of the Dateadd function
• 203665: Database changes are not shown in the Action center tab after the linking process is done for databases containing values inside square brackets as a part of the Dateadd function
• 204020: Database changes are not shown in the Action center tab after the linking process is done for databases containing the Reseed value inside quotes as a part of the Dbcc checkident command
• 204249: Objects containing the 'con' in the name will be shown without names in the Action center tab after upgrading to the 2021.01.2063 add-in version
• 204250: The latest object state is not shown in the Action center tab after upgrading to the 2021.01.2063 add-in version if the label exists on the repository
• 203565: ''Database %database% not accessible for the user 'username''' error is encountered when the Encrypt connection and Trust connection options are checked under the Connection Properties tab in the Connect to Server dialog

Known limitations:

• Objects containing Windows reserved words in their name and committed to source control with the 2021.01.2063 or 2021.01.2072 add-in versions are shown in the Action center tab as non-existing on both sides and history for those objects is not accessible
• An object containing special characters in the schema name is shown as non-existing on a database side in the Action center tab after the initial commit is finished
• "TortoiseSVN version is not supported" message is shown when the Browse for folder button is clicked in the Source control setup window when working with the TortoiseSVN client version higher than 1.9
• ''Database <database_name> not accessible for the user 'username''' message is shown when the Link to source control right-click database command in the Object Explorer panel is clicked for a database with an apostrophe in its name

Fixes:

• 203384: "The path is already mapped in workspace" error is encountered when the Browse for folder button, under the System login tab in the Source control setup window, is clicked for Azure DevOps Server and a non-default collection is chosen
• 203385: "Object reference not set to an instance of an object" error is encountered when the Browse for folder button, under the System login tab in the Source control setup window, is clicked for Azure DevOps Server and the chosen collection is offline