ApexSQL Source Control patch release notes

Fixes:

• 228043: Fixed the issue preventing signing up when using Windows authentication to connect to an on-premise Team Foundation Version Control
• 228042: Database changes not showing in the Action center when (NOLOCK) is used in front of the identifier

Fixes:

• 226193: "Parse error: [ ,MIN(CAST(E.[SessionDate] AS DATETIME)" error is encountered when linking a table and function which convert time to UTC to the Source Control
• 225931: "Parse error: [Incorrect syntax near ''YMD''] at [position: 175, line: 11, column: 16]" error is encountered when a stored procedure with date format YMD is run
• 222644: “Parse error: [Incorrect syntax near '@TargetPartition'] at [position: 177, line: 11, column: 19]“ error is encountered when synchronizing a SQL database with the repository in a specific case
• 225838: "Parse error: [OPTION (MAX_GRANT_PERCENT = .25);] at [position: 130, line: 10, column: 29]" error is encountered when linking a database to repository with created stored procedure that include OPTION (MAX_GRANT_PERCENT = .25);
• 224994: "Parse error: [Incorrect syntax near 'tablock'] at [position: 1123, line: 32, column: 36]" error is encountered when linking a SQL database with the repository in a specific case
• 221963: "Parse error: [DBCC FLUSHPROCINDB (1);] at [position: 172, line: 8, column: 21]" error is encountered when using DBCC FLUSHPROCINDB while creating a procedure
• 221192: “Parse error: [Incorrect syntax near 'from'] at [position: 8071, line: 186, column: 4]“ error is encountered when synchronizing a SQL database to the repository in a specific case

Fixes:

• 210739: Only objects from the first linked Azure SQL Database in the shared development model can be checked out and locked

Fixes:

• 208737: Partition schema references are not present in a table script in the Action center tab for SQL Server 2016
• 208738: Filestream references are not present in a table script in the Action center tab for SQL Server 2016
• 208240: "Invalid object name 'SYS.EXTENDED_PROPERTIES'" message is shown when the Finish button in the Source control setup window is clicked for a database with the case sensitive collation

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
• Excluded objects present only on the source control repository are shown in the Action center tab after SQL Server Management Studio is restarted