ApexSQL Source Control release notes

Fixes:

• The "Failed to login. Internet connec􀆟on is required to con􀆟nue. Click Retry to try again" error is encountered on applica􀆟on start
• 226193: "Parse error: [ ,MIN(CAST(E.[SessionDate] AS DATETIME)" error is encountered when linking a table and func􀆟on which convert 􀆟me to UTC to the Source Control
• 225931: "Parse error: [Incorrect syntax near ''YMD''] at [posi􀆟on: 175, line: 11, column: 16]" error is encountered when a stored procedure with date format YMD is run
• 222644: “Parse error: [Incorrect syntax near '@TargetPar􀆟􀆟on'] at [posi􀆟on: 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 [posi􀆟on: 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 [posi􀆟on: 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 [posi􀆟on: 172, line: 8, column: 21]" error is encountered when using DBCC FLUSHPROCINDB while crea􀆟ng a procedure
• 221192: “Parse error: [Incorrect syntax near 'from'] at [posi􀆟on: 8071, line: 186, column: 4]“ error is encountered when synchronizing a SQL database to the repository in a specific case
• 228043: Fixed the issue preven􀆟ng signing up when using Windows authen􀆟ca􀆟on to connect to an on-premise Team Founda􀆟on Version Control
• 228042: Database changes not showing in the Ac􀆟on center when (NOLOCK) is used in front of the iden􀆟fier
• 230056: Applying a substan􀆟al number of objects to a repository results in an unsuccessful commit

Fixes:

• 220449: "[Incorrect syntax near '=']" at [position: 476, line: 14, column: 61] error is encountered when synchronizing SQL database to the repository
• 214465: Database changes are not shown in the "Action center" tab' after the linking process is done for databases containing procedures with the "at time zone" statement
• 213718: The delay of 5 s in opening a new query appears when 20 databases are linked to the source control repository
• 199133: The right-click context menu commands are not applicable on the group header in the "Action center" tab when the groups are collapsed
• 206823: Excluded objects present only on the repository side are shown in the "Action center" tab after SSMS restart
• 208019: Database changes are not shown in the "Action center" tab after the linking process is done for databases containing procedure with the output parameter defined without the square brackets in a script
• 208020: Database changes are not shown in the "Action center" tab after the linking process is done for databases containing an object with formatted query result as JSON without ROOT node name defined in a script
• 208255: "Parse error: [Incorrect syntax near 'UPDLOCK']" error is encountered when try to link a database
• 209263: Database changes are not shown in the "Action center" tab after the linking process is done for databases containing objects with the number formatted as <number>.e<number> in a script
• 216490: Action Center doesn’t show static data for tables with custom schema owners
• 206195: "No committed changesets" error is encountered when the "Object Explorer" panel right-click context menu "Project history" command is clicked after the initial commit is finished for the Perforce source control system
• 205923: "Make sure correct username and password are specified" error is shown when the Test or Finish button is clicked in the Source control setup window for Perforce when linking a second database to the same workspace and depot
• 221076: Credential object type is missing under the "Object filter" tab in the "Options" window
• 221327: "Parse error: [Incorrect syntax near '@locale'] at [position: 820, line: 26, column: 53]" is encountered when trying to link database to Git repository hosted on Azure Services
• 214465: Database changes are not shown in the "Action center" tab after the linking process is done for databases containing procedures with the "at time zone" statement
• 221076: Credential object type is missing under the "Object filter" tab in the Options window

Changes:

• The activation model is switched to Subscription
• The application does not support integration into SQL Server Management Studio 2012, 2014, and 2016 versions

Known issues

• 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

Enhancements:

• SQL graph tables support
• Temporal tables support
• Delete button is added in the Labels window
• Refresh button is added in the Labels window

Fixes:

• 204610: The labels created on the Subversion repository using the File authentication are not shown in the Labels window
• 202359: ''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
• 204550: ''One or more errors occurred'' error is encountered when the Get button is clicked in the Labels window for a label created on a root of the Git repository
• 205736: An object is listed for deletion from a database in the Get changes from the repository window after the Get button is clicked in the Labels window when all objects on which it depends are not a part of the selected label
• 206194: "The path is not of a legal form" error is encountered when any other changeset is selected after the initial commit changeset in the Object history window
• 206202: ''Connection failed with message: 'The path is not of a legal form''' error is encountered when a non-existing string is typed in the text filter for any object grid column in the Project or Object history window
• 206330: The name of an object with the migration script is shown as .%object_name% in the Migration scripts dialog after the migration script is being edited
• 206199: The Script errors dialog is shown when the Get or Get changeset button is clicked in the Project or Object history window for a changeset related to label creation or deletion on the Subversion repository
• 205996: ''One or more errors occurred'' error is encountered when the Get button is clicked in the Labels window for a label created on a root of the Mercurial repository
• 205737: The Project history window closes when the Get changeset button is clicked for a changeset that does not contain all dependent objects for a database linked to a repository root
• 206211: ''Nothing to sync between the source control and database versions'' error is encountered when the Get changeset button is clicked in the Project history window for a previously committed static data change
• 206205: The script for the first object on the list of the selected changeset is shown in the Object history window
• 206158: The add-in’s object status icons and right-click context menu commands are shown on the sub-object level in the Object Explorer panel
• 206066: The Action center tab is opened after SQL Server Management Studio restart even though the credentials are not present in the Connect to source control dialog
• 206203: ''Connection failed with message: 'Value cannot be null. Parameter name: path2''' error is encountered when a non-existing string is typed in the text filter for any changeset grid column in the Project or Object history window
• 206072: The static data is shown as conflicted in the Action center tab for the second database linked in the dedicated model to the same repository
• 205997: A database can be linked to the Azure DevOps Server/Services repository root
• 206020: All objects from a database are shown in the Object filter grid in the Object filter tab of the Source control setup window after the object filter is imported
• 206660: Filter options in the Object filter tab under the Source control setup and Options window do not work
• 198750: “System.OutOfMemoryException” error is encountered when the Create button is clicked in the New label window for a database linked to the Azure DevOps Server repository in the shared development model and there are more than 10K labels
• 204313: The Show/Hide objects button under the Object filter tab in the Source control setup window does not respond if in the same session the development model is changed
• 200240: The Action center tab is not fully visible on Full HD display resolution (1920x1080) and 150% scaling
• 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
• 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
• 204272: ''Database '%database name%' not accessible for the user '%username%''' error is encountered when the Link database to source control right-click Object Explorer panel context menu command is clicked in SQL Server Management Studio 18 and ApexSQL Analyze is integrated as well

Changes:

• Create label and Show labels commands under the right-click Object Explorer panel context menu are now replaced with the Labels command
• Object filter and Script options tabs are now under the Advanced options tab in the Source control setup window

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

Enhancements:

• Performance of the Action center tab has been improved up to 280%
• New framework object for both development models is added
• Additional ignore comparison options are added under the Script options tab:
  • Server and database names in synonyms
  • Next filegroups in partition schemas
• Additional synchronization options are added under the Script options tab:
  • Include dependent objects
  • Script USE for database
• Static data resolve conflict support
• New ApexSQL Updater allows users to configure advanced updating settings of all installed ApexSQL products
• Application telemetry now collects anonymous data on the use and performance of applications and application components

Fixes:

• 199093: “The ‘Stub’ package did not load correctly” warning message is shown on SQL Server Management Studio startup after the add-in installation
• 187619: The static data remains listed in the Action center tab after applying it against a database linked to the working folder
• 168784: The Object Explorer right-click database source control context menu is shown only for the first selected database from a connected SQL Server
• 177730: ''Policy Warning. Internal error in Changeset Comments Policy'' error is encountered when committing changes to the Azure DevOps Services repository and the commit comment policy is set
• 169832: Switching between the Options tab is not possible if the linked database is not selected in the Object Explorer panel before the Options main menu command is clicked
• 182664: ''Make sure correct username and password are specified'' error is encountered when the Finish button is clicked in the Source control setup window for the Git repository hosted on the BitBucket.org or GitHub service using the SSH authentication
• 187993: The repository script is not shown in the Action center tab for procedures that contain the Alter table and Drop if exists statements in that order
• 192734: ''Commit failed and changes will not be applied'' error is encountered when the Apply button is clicked in the Action center tab for objects created under the aux schema
• 193836: ''SELECT failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL''' error is encountered when an object is altered using the Concat null yields null statement if the ApexSQL_SourceControl_DDL trigger is present on a Server level
• 193990: ''Error occurred updating database object: Parse error: Object reference not set to an instance of an object'' error is encountered when applying a procedure created under the usercreated schema against a database linked to a working folder
• 200041: An object can be edited without been previously checked out and locked even though when the Restrictive database policy is set
• 185108: '''ApexSQL_SourceControl_DDLTrigger' missing. Re-link database to track changes'' error is encountered on every click for SQL Server 2008 SP4 database linked in the shared development model
• 178410: Changes can be committed by the other user when the Restrictive database policy is set and the Commit other user changes option is not enabled for a database linked in the shared development model on the Azure DevOps Server
• 179247: The maximal value of the Number of changesets shown in the ''History'' form option is limited to 1,000 changesets
• 180249: ''Could not select repository '' on Server'' error is encountered when the Browse for folder button is clicked in the Source control setup window for the Azure DevOps Server when using Token
• 181591: The collation part is not shown in the object script in the Action center tab when the Collations option is checked under the Script options in the Options window
• 181594: The Latin1_General_CI_AS_KS_WS collation is generated in the synchronization script regardless of the set database collation when the collation is not specified in the repository script
• 179234: The object status for the user object type does not follow the check status for a database linked in the shared development model
• 179246: All committed changesets to a source control repository are shown in the Object history window
• 180927: The exported excluded objects list will be different if previously is clicked the Show objects button in the Local settings tab of the Options window
• 167076: "Could not connect to Server 'https://dev.azure.com/' with message: 'Method not found: 'Void..." error is encountered when the Finish button is clicked in the Source control setup window for the Azure DevOps Services
• 167873: "Make sure correct username and password are specified" message is shown when the Finish button in the Source control setup window is clicked for the Git repository hosted on the GitLab service using the SSH authentication
• 168613: "Changes were not applied" message is shown when the Get button is clicked in the Labels dialog
• 129467: "Make sure that correct username and password are specified" message is shown when the Finish button is clicked in the Source control setup window for the Git repository hosted on the Bitbucket Server when using the SSH authentication
• 152841: ''To commit changes reenter password'' message is shown when the Apply button is clicked in the Action center tab for the Git repository hosted on the BitBucket.org service when using the SSH authentication
• 152849: The getting latest from source control step in the Action center tab never ends for the public Git repository hosted on the BitBucket.org service when using the SSH authentication
• 157548: The Acton center tab cannot be opened if previously is closed using SQL Server Management Studio shortcut
• 163799: The object status is not updated in the framework object tables for the shared development model
• 164177: Object history window is not functional in high DPI and 4K resolution
• 164179: Project history window is not functional in high DPI and 4K resolution
• 165004: SQL Server Management Studio restarts when the Finish button in the Source control setup window is clicked for the Git repository hosted on the BitBucket.org service when using the SSH authentication
• 166021: SQL Server Management Studio closes when the Finish button is clicked in the Source control setup window when a database is linked to a new empty Git repository hosted on the GitLab service when using the SSH authentication
• 166904: "Object reference not set to an instance of an object" error is encountered when the Get changeset button is clicked in the Project history window
• 167069: Framework objects are not dropped after the unlinking process is done for the Azure SQL Database linked in the shared development model
• 192942: Data compressed tables are scripted as partitioned tables, when any other filegroup under a table is not created, is set as a default one
• 199832: The add-in options are not present in the Object Explorer right-click context menu for any object in the linked database
• 76737: "SystemOutOfMemory exception" error is encountered when applying changes against a database with more than 8,000 objects
• 87834: SQL user created from a login is scripted as a SQL user with a password when applying changes against a database
• 88077: Additional empty lines are shown as a difference in the edited object script for a database linked to the Team Foundation Server 2017 repository
• 94386: An object change cannot be applied against a database if the only difference is white space
• 94387: The Get changes from the repository window will not be open when the Check constraint change is applied against a database
• 95081: Table columns will not be scripted in the Action center tab after a table is dropped and re-created and one column is set to be nullable
• 111194: An object will be shown as a conflicted one in the Action center tab after switching branch for a database linked to the Subversion repository
• 115873: ‘’Object references not set to an instance of an object’’ error is encountered when the Action center tab is opened by the user with the lack of permissions
• 120507: Linked static data will become unlinked after connecting to a SQL Server with another login and connect back with the same login used to link a database
• 123542: The static data remains in the Action center tab after being committed if in the same changeset the custom and migration script are committed as well
• 125085: "Commit failed! Check log for more details" error is encountered when the Apply button is clicked in the Action center tab by a user that has the minimal required permissions
• 149571: The Connect to source control window is shown after every button-click for the Git repository hosted on the Azure DevOps Services
• 152639: SQL Server Management Studio becomes unresponsive when the Refresh button in the Action center tab is clicked for a database with 10,000 objects
• 155462: Ignore comparison options are not loaded when the My default button is clicked in the Source control setup window
• 157571: The add-in Export folder is created wherever the SQL Server Management Studio shortcut exists on the machine
• 157624: The Action center tab cannot be open using the Ctrl+Shift+X keyboard shortcut if it is previously closed using the Alt+F4 keyboard shortcut
• 159525: The Action center tab does not detect the custom script folder unlink change
• 163811: The shortcuts under the Shortcuts tab of the Options window cannot be disabled
• 164220: The resolve conflict window is not shown when single object changes are committed to the repository using the Commit changes command from the Object Explorer panel right-click context menu
• 164923: SQL Server Management Studio becomes unresponsive when branches are merged
• 164930: SQL Server Management Studio becomes unresponsive when the Refresh button is clicked in the Action center tab for a database linked to the Git repository hosted on the BitBucket.org service when using the SSH authentication
• 164932: The Insert scripts are not executed when applying changes against a database
• 164938: The Migration script window is closed when the Edit button is clicked
• 164939: The Add migration script right-click context menu command in the Action center tab is missing after the previously created migration script is deleted for that table
• 166794: "Specified project '$/<project_name>' not available. Ensure that project exists and is available" error is encountered when the Refresh button is clicked in the Action center tab for a second database linked to the same repository
• 166889: "Cannot create branch '$/test-branch1'. The item $/branch already exists" message is shown when the Create button in the Create branch window is clicked for the Azure SQL Database
• 167207: "Make sure correct username and password are specified" message is shown when the Finish button is clicked in the Source control setup window for the Git repository hosted on the Azure DevOps Services
• 167395: "Credentials are not valid" message is shown when the Finish button is clicked in the Source control setup window for the Azure DevOps Services when the Use Windows authentication option is checked
• 167634: A changeset is not present in the Merge branches dialog when change is committed to a newly created branch for the Git repository when using the File authentication
• 168278: ‘’Passphrase filed is empty or the passphrase not valid’’ message is shown when the wrong URL is typed in the Source control setup window and the Finish button is clicked for the Git repository when using the SSH authentication
• 168609: The Migration script window is closed when the Edit button is clicked for the existing migration script
• 168680: "Depot with name '$/DepotName' doesn't exist on this server" message is shown when the Browse for folder button is clicked in the Source control setup window and folder path is already present in the Project filed for the Perforce server
• 200240: The Action center tab is not completely visible on full HD resolution (1920x1080) and 150% scaling
• 178559: "Could not select repository "on Server" error is encountered when the Finish button is clicked in the Source control setup window for the Azure DevOps Server when using the wrong credentials

Changes:

• Error handling and send logs functionality has been modified
• ApexSQL defaults, My defaults, and Save as my defaults functionality has been modified
• Ignore comparison options tooltips are clickable now and they show examples for each option
• Minimal required SQL Server permissions to work with ApexSQL Source Control are changed
• Minimal required Azure SQL Database permissions to work with ApexSQL Source Control are changed
• Minimal required Amazon RDS for SQL Server permissions to work with ApexSQL Source Control are changed
• Merge branches option is now supported only for the Git source control system

Known limitations

• "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

Enhancements:

• Display of the right-click context menu in the Object Explorer panel for Azure SQL Database is faster for 100%

Fixes:

• Changes will be committed to the online Git repository even when working in the offline mode

Known limitations:

• "Make sure that correct username and password are specified" message is shown when trying to link a database to the Git repository hosted on the Bitbucket Server using the SSH authentication
• SQL Server Management Studio stops working when linking a database to Git repository hosted on the BitBucket.org using the SSH authentication and SSH keys are created with the Command Prompt
• "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
• SQL Server Management Studio freezes when the Confirm button is clicked in the Merge branches window for merging branches
• "Specified project '$/<project_name>' not available. Ensure that project exists and is available" error is encountered when the Action center tab is refreshed for the second database with the same name and linked to the same repository

Enhancements:

• Object status icon for linked static data is added in the Object Explorer panel
• SQL Server 2019 support
• Getting entire changeset in the Project History window is faster by 6,000%

Fixes:

• The initializing progress bar never ends in the Action center for shared database after importing connection
• "Get latest version failed with the message" error is encountered when the Action center tab starting after importing connection for database linked to the VSTS repository
• 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 SQL Server Management Studio 18, even though it's currently running
• "Changes were not applied" error is encountered when the label is applied for the Azure DevOps repository hosted on the Azure DevOps Server
• Changes can be committed to the Azure DevOps repository without specified work item, even though the work item policy and the comment policy are set for that repository
• The White space ignore comparison option under the Action center tab does not work with views
• "AT" alias is deleted in the synchronization script when applying changes against a database
• A database object can be deleted, even if it is not checked out and locked when the Restrictive database policy is set for database linked in the shared development model
• Table index containing the Include clause is not scripted correctly in the Action center tab
• New object cannot be created when the restrictive policy is set for database linked in the shared development model
• The Connect to source control window is not show in the Action center tab after SQL Server Management Studio is restarted for a databases linked to the Git repository using the SSH authentication
• "ApexSQL_SourceControl_DDL Trigger is missing" error is encountered when linking a SQL Server 2005 database to Azure DevOps Server repository
• "Merge successful" message is shown when the OK button is clicked in the Merge branches window, even when the branches are not merged
• "Object reference not set to an instance of an object" error is encountered when applying changes against a database linked in the dedicated model to the Git repository hosted on GitHub
• The Action center tab hangs after SQL Server Management Studio is restared for a databases linked in the shared development model
• "The given path's format is not supported." error is encountered when linking a database to a source control repository from a SQL Server that has ':' in its name
• The Resolve conflict window is shown when two branches are merging for Git repository hosted on Azure DevOps Services
• "Object references not set to an instance of an object" error is encountered when linking the Wide World Importers database to source control
• "Object reference not set to an instance of an object" error is encountered when applying changes against a database linked in the dedicated model to the Git repository hosted on GitHub
• The add-in commands appear in the right-click context menu in the Object Explorer when connected to a SQL Server Analysis Services or SQL Server Reporting Services or SQL Server Integration Services
• Scripts for the renamed table are not shown in the Differences preview window in the Action center tab
• "ApexSQL Source Control - Permissive policy is enabled on this database. Object must be checked out before editing" error is encountered when changes made against a locked object are reverted and the Restrictive policy option under the Administration tab of the Options window is enabled
• The Action center tab does not recognize adding custom scripts as a change
• All objects are shown as not committed in the Action center tab after importing connection for a database linked to the Subversion repository
• SQL Server Management Studio stops working when connecting to SQL Server with the Active Directory - Universal with MFA support authentication

Known limitations:

• "Make sure that correct username and password are specified" message is shown when trying to link a database to the Git repository hosted on the Bitbucket Server using the SSH authentication
• SQL Server Management Studio stops working when linking a database to Git repository hosted on the BitBucket.org using the SSH authentication and SSH keys are created with the Command Prompt
• "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
• SQL Server Management Studio freezes when the Confirm button is clicked in the Merge branches window for merging branches
• "Specified project '$/<project_name>' not available. Ensure that project exists and is available" error is encountered when the Action center tab is refreshed for the second database with the same name and linked to the same repository

Changes:

• 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

Fixes:

• "There is no information about previous state of the object" message is shown when the Undo button is clicked in the Action center tab
• Object status icons in the Object Explorer pane does not show correct object status
• "User" does not have the following permissions to link the database in dedicated model'' error is encountered when linking database with dot in its name
• Connecting to repository process never ends when linking a database to Git repository hosted on Azure DevOps Server
• The Edited by column in the Action center tab does not contain any information
• The Connect to source control window is shown for a database linked to a Mercurial repository using file authentication

Known limitations:

• Send logs window is shown when the Object history window is started for Azure SQL Database service
• "Make sure correct username and password is specified" message is shown when linking to Git repository hosted on GitLab over SSH authentication
• Database object scripts are not shown in the Project history window for Azure SQL Database service
• "Make sure correct username and password is specified" message is shown when linking to Git repository hosted on GitLab over SSH authentication
• "Make sure that correct username and password are specified" message is shown when linking to Git repository hosted on Bitbucket Server over SSH authentication

Fixes:

• "There is already an open DataReader associated with this Command which must be closed first" error is encountered when expanding any node in SQL Server Management Studio’s Object Explorer while connected to an SQL Server hosted on an Azure VM
• The add-in does not integrate in SQL Server Management Studio when installed in parallel with any other ApexSQL add-in product released after April 02, 2019

Fixes:

• The add-in doesn't integrate with SQL Server Management Studio 18 GA version

Enhancements:

• The time for showing all database objects in the Object filtering tab of the Source control setup window has been improved by up to 567%
• The time for showing the Action center tab after the Finish button is clicked in the Source control setup window has been improved by up to 50%

Fixes:

• The repository credentials are required after the unlinking process is done for a database linked to the Azure DevOps repository
• "Make sure correct username and password is specified" message is shown when linking to the Git repository hosted on Azure DevOps Services over SSH authentication
• ApexSQL_SourceControl schema is shown in the Action center tab as an object that can be changed
• "Could not get value for key 'password'" error is encountered when linking a database to Code Commit hosted on Amazon RDS for SQL Server
• "Abort: http authorization required" error is encountered when linking a database to the Mercurial repository hosted on RhodeCode
• The Action center tab cannot be started when the framework database name contains hyphen
• ApexSQL Source Control framework objects are listed in the Object filtering tab for Azure SQL Databases
• "Could not find a part of the path" error is encountered when any source control repository becomes unavailable
• "Error in cleaning directory" error is encountered when the same database is unlinked and then linked in one SQL Server Management Studio session
• "Credentials are not valid" message is shown when the Refresh collections button in the Source control setup window is clicked for Azure DevOps repository and the default Azure DevOps collection is offline
• "The activation key invalid for this version" error is encountered when the eligible license key for ApexSQL Source Control 2018 versions is used for activation
• The Action center tab is refreshed after label applying is canceled
• The Show only different rows option is applied in the Project history window
• SQL Server Management Studio stops working when the Show auto filter rows option from the Action center tab context menu is clicked
• SQL Server Management Studio goes to not responding state when database objects are right-clicked in the Action center tab for a database with more than 18,000 objects
• SQL Server Management Studio goes to not responding state when trying to change the action with a click on the action arrow under the Action column in the Action center tab for database with more than 18,000 objects
• "Make sure correct username and password is specified" message is shown when linking to Git repository hosted on BitBucket.org over SSH authentication

Changes:

• Object status icon color for the other user on a shared database is now purple

Known limitations:

• "Make sure correct username and password is specified" message is shown when linking to Git repository hosted on GitLab over SSH authentication

Fixes:

• Changes made against object containing CTE are not recognized in the Action center tab
• The Choose project window for the Mercurial repository is opened when the Test button is clicked in the Source control wizard
• "SystemOutOfMemory exception" error is encountered when the database node in the Object Explorer panel is expanded if more than 20 databases are linked to source control
• "The activation key invalid for this version" error is encountered when the eligible license key for 2018 add-in version is used for activation
• "The Delete statement conflicted with the reference constraint" error is encountered when applying static data changes from a repository against a database
• "Full-Text Search is not installed, or full-text component cannot be loaded" message is shown when changes are applied against a database even when the Full-Text Search feature is installed on SQL Server
• Database with special characters in its name cannot be linked to source control
• SQL Server Management Studio restarts when the Show objects command under the Global settings tab of the Options window is clicked on for databases with custom scripts folder linked
• "Cannot create branch" error is encountered when click on the Create button in the Create branch window for the Git repository
• "Make sure correct username and password are specified" message is shown when linking a database to the Git repository hosted on GitHub over SSH authentication
• New SQL Server cannot be chosen in the Import connection tab of the Options window
• The project in the Choose project window cannot be deleted for an Azure DevOps Server repository
• "Object reference not set to an instance of an object" error is encountered when applying a label against a database
• "The ApexSQL_SourceControl_DDL Trigger is missing" message is shown for SQL Server 2008 R2 databases linked in the shared development model
• The add-in recognizes only default branch for the Mercurial repository
• "Cannot create branch. One or more errors occurred" error is encountered when creating a new branch for the Azure DevOps Server repository
• Branches are not listed in the Select branch window for the Azure DevOps Server repository
• "The custom script folder is linked to source control" message is shown when the custom script folder is unlinked from source control
• Deleted Azure DevOps Server team project is shown as string of random numbers in the Choose project window
• "Make sure correct username and password are specified" message is shown when linking a database to Git or Subversion repository hosted on CloudForge
• "Changes cannot be applied" message is shown when label is applied against a database with FullText index
• "Changes were not applied" message is shown when applying changes against object with FullText index on SQL Server Express edition, if the Full-Text Search feature is not installed on SQL Server
• The comment field in the Action center tab is disabled when commit comment contains only numbers

Enhancements:

• Showing static data differences for scripts containing more than 1000 different rows is improved by 6000%

Fixes:

• "Unable to connect to TFS server" error is encountered when using https://dev.azure.com URL to link to the Team Foundation Server repository hosted on Visual Studio Team Services
• SQL Server Management Studio is restarted when the Link database to source control context command is selected for any SSAS database
• "Could not connect to the server" message is shown when the Action center tab button is clicked for a database linked to the Team Foundation Server repository hosted on Team Foundation Server
• Team Foundation Server work item check-in policies do not work
• Team Foundation Server comment check-in policies do not work
• "The specific check-in policies are enabled and not satisfied" error is encountered when committing to the Team Foundation Server repository
• SQL Server Management Studio is restarted when any database is right-clicked under Analysis Services in the Object Explorer panel
• "No source control labels found" message is shown when the Show label command is clicked on, even if there are created labels on Git repository hosted on BitBucket.org
• "Item '$/TeamProject' is obsoleted" error is encountered when creating a new project for the Team Foundation Server repository hosted on Team Foundation Server
• SQL Server Management Studio restarts upon refreshing the Action center tab after the Project history window is closed
• "There is no information about previous state of the object" message is shown when the Undo button is clicked in the Action center tab
• "TF200016: The following project does not exist" error is encountered when creating a new project on Visual Studio Team Services using the alternate credentials
• The commit messages are missing from the Project history window
• "The ApexSQL_SourceControl_DDLTrigger is missing" message is shown when starting the Action center tab for Amazon databases linked in the shared development model
• SQL Server Management Studio is restarted when the auto filter row is shown in the grid and the header of the Action column is clicked on
• "Get by version failed during copying files/folders to destination" error is encountered when applying changes against a database from the Project history window
• "Object reference not set to an instance of an object" error is encountered when the Options window is started
• The Source control setup window is closed when in the project path field is entered the repository URL for Git hosted on BitBucket.org
• The object filtering settings are saved correctly only the first time they are exported
• "Failed to authenticate the Visual Studio Online account" error is encountered when linking database to Git repository hosted to Visual Studio Team Services company private account
• The Choose project window is closed when the New button is clicked on
• The filter for the Action column in the Action center tab will not open when the focus is on the action arrow
• "An error occurred when updating the database object" error is encountered when revert changes made against an object in the Action center tab when the Undo button is clicked on
• "Unable to connect to this Team Foundation Server" error is encountered when starting the Action center tab for database linked to the Team Foundation Server repository hosted on Team Foundation Server after SQL Server Management Studio is restarted
• Created Labels are seen in different project on Mercurial repository on Bitbucket.org
• "Edit migration script" command is shown in the Action center tab context menu when the migration script is not present for the selected table
• "Object reference is not set to an instance of an object" error message occurs when the Action center tab is started on one database and then change it and start on another database
• The action in the Action center tab is changed after the commit has failed to the Team Foundation Server repository
• "The chosen repository is not available" message is shown when the Action center tab is started for the first time after SQL Server Management Studio restart for databases linked to Git public repository hosted on GitHub
• Project information is not checked in the Source control setup window when linking database to Subversion repository
• "The process cannot access the file 'C:\Users\%user%\AppData\Local\ApexSQL\ApexSQL Source Control' because it is being used by another process." error is encountered when trying to link a database to Git repository hosted on Bitbucked.org
• The Select all command in the Object filtering grid selects group headers
• "Exception caught during the push command" error is encountered when committing to Git repository hosted on BitBucket.org after changing the location of working copy of repositoryy
• Data for the linked database is not moved to new location when the working copy of repository path is changed
• "The 'ApexSQLSourceControl_instPackage' did not load correctly" message is shown on SQL Server Management Studio 18.0 (preview) startup when the application is installed on a system that has no 17.9 and older host version installed
• "Policy warning. Internal error in Work Items" error is encountered when committing changes to the Team Foundation Server repository without specifying the work item
• "Exception caught during the push command" error is encountered when committing to Git repository hosted on BitBucket.org after changing the location of working copy of repository
• "Exception caught during the push command" error is encountered when committing to Git repository hosted on BitBucket.org after SQL Server Management Studio is restarted
• "An error was encountered and the application needs to be closed" error is encountered when the Action center tab is started for the database linked to the Team Foundation Server repository hosted on Team Foundation Server
• "Some ApexSQL Source Control framework objects were not created successfully" error is encountered when linking SQL Azure Database in the shared model
• "Framework objects will be upgraded" message is shown when clicked on a linked database from the Object Explorer pane
• "An exception occurred USE statement is not supported to switch between databases. Use a new connection to connect to a different database" error is encountered when azure database is linked in the shared development model
• Changes made against static data are not shown in the Action center tab, in case the static data script has more than 1000 rows
• SQL Server Management Studio becomes unresponsive in case the static data from a table with the large amount of data is linked and committed to the repository

Known limitations:

• The project cannot be deleted from the Choose project window for the Team Foundation Server repository hosted on Team Foundation Server
• SQL Azure Database with a special character in its name cannot be linked to source control

Changes:

• The application now requires Microsoft .NET Framework 4.7.2

Fixes:

• "Cannot update temp storage" error is encountered when committing changes to the Git repository after changing the location of the working copy of the repository
• "Credentials are not valid" message is shown when linking a database to a TFS repository hosted on Team Foundation Server 2013
• "No source control labels found" message is shown when the Show label command is clicked on even if there are created labels on Git repository
• "The database cannot be used for storing ApexSQL Source Control framework objects" message is shown when linking an Amazon database in the shared model
• Imported Object filtering options are not shown until additional changes are made
• Labels are not shown if the spacing between words is used in name of the label for Subversion source control system
• Setting a Windows default shortcut for an action disables application shortcut
• The Get updates option does not work after expiration of trial

Enhancements:

• SQL Server 2019 CTP 2.0 support
• SQL Server Management Studio 18 integration support

Fixes:

• "The type initializer for ApexSQL Source Control threw an exception" error is encountered when ApexSQL Refactor 2018.03 is installed and the Options dialog is started
• "The culture ‘[regional culture name]’ is not supported" error is encountered when operating system is set to a non-English regional language settings
• "Credentials are not valid" message is shown when linking a database to a TFS repository hosted on Azure DevOps

Enhancements:

• Improved application installer with a dark theme
• New application icon
• High DPI and 4K resolution support
• The whole changeset can be reverted from the history form

Fixes:

• The option settings are not remembered when the Options dialog is closed
• SSMS restarts when trying to link database with ''|'' in its name
• "Some ApexSQL Source Control framework objects were not created successfully, attempt to relink the database to source control and inspect the add-in log for detailed information" message is shown when linking Azure database to Git repository hosted on GitLab via SSH authentication
• "Make sure correct passphrase or key pair path is specified" error is encountered when try to link a database to Git repository hosted on GitLab via SSH authentication
• Assemblies cannot be added to the migration script
• "Could not find part of the path" error is encountered when linking database to Perforce source control system
• "Error in localize options:Sequence contains no elements" error is encountered when trying to import connection for shared databases
• "Make sure correct username and password are specified" message is shown when try to link a database to Git repository hosted on Team Foundation Server
• The Source control setup window loses the theme after uninstalling ApexSQL Diff or ApexSQL Data Diff
• "The specified folder doesn't have the appropriate structure" message is shown when linking to a repository created with older versions of the add-in
• "Incorrect repository path is used for Git" message is shown when linking a database to Git repository hosted on Bitbucket.org
• "Changes were not applied" error is encountered when applying a label against a database if Full-Text and Semantic Extraction for Search is not installed on SQL Server
• The Labels window appears when the ‘’Check in’’ command is clicked on from the Object Explorer pane context menu
• SSMS restarts when the Options dialog is closed on the Close (X) button
• Initially committed modified objects under dbo schema are shown in the Action center tab like new objects that have never been committed
• "Changes were not applied" error is encountered when applying label against a database
• "Commit failed! check log files for more details" error is encountered when trying to perform initial commit to Subversion repository using the svn:// URL format
• The "Check all" context menu command in the Action center tab should check only the visible objects from the list
• The newly created labels containing special characters in names are not listed in the Show labels window
• The second commit to TFS repository hosted on Team Foundation Server doesn't work
• "Make sure that correct username and password are specified" message is shown when try to link a database to Git repository hosted on Team Foundation Server via SSH authentication
• "Policy Warning. Internal error in 'policy name'" error is encountered when checking in changes without following the rule enforced with the Team Foundation Server policy
• "The process was terminated due to an unhandled exception." error is encountered when ApexSQL Search 2016.07.0080 is installed as well
• The Source control setup window closes when trying to choose another branch under the System login tab from the Git repository hosted on BitBucket.org
• "Some ApexSQL Source Control framework objects were not created successfully" message is shown when linking database in the shared development model to Git public repository hosted on BitBucket.org
• "The ApexSQL Source Control Trigger is disabled" message is shown when the Action center tab is started for shared databases after restarting SSMS
• The changed option settings are remembered in the General tab of the Options dialog when the ECS keyboard key is pressed
• The filtered object settings in the Object filtering tab of the Options dialog are remembered when the ECS keyboard key is pressed
• All changes made in the Options dialog should be saved automatically when the OK button is clicked on
• SSMS restarts when applying changes from the repository against a database
• "At least one database must be linked to access the "Script options" tab" message is shown when the My defaults button is clicked on in the Options dialog
• The "Owners in synchronization script" option settings are not remembered on closing the Options dialog
• "The type initializer for 'ApexSQL.Common.Misc.ProductInfo' threw an exception." error is encountered when the "Send log" option is clicked on
• "The chosen repository is not available" error is encountered when the Action center tab is started for a database linked to TFS repository hosted on Azure DevOps if the password is not remembered in the Source control setup
• "Object references not set to an instance of an object" error is encountered when trying to commit changes to Git repository hosted on BitBucket.org
• "Could not connect to the server" error is encountered when linking a database to TFS repository hosted on Azure DevOps
• The Object explorer pane context menu commands do not work for database schemas
• The Database dropdown list in the Administration tab of the Options dialog should not be disabled when SQL Server without linked databases is chosen
• ExamDiffPro merging window starts empty when chosen as a default merging tool
• The "Apply changes" option is saved on clicking the Cancel button in the Options dialog
• The "Case" ignore comparison option does not work
• Incorrect SQL migration script can be created in the Add migration script window
• "Could not find file 'C:\Windows\System32\sc.txt'" error is encountered when click on a custom script in the Project history window
• "Method not found" error is encountered when the Get updates command is clicked on
• The Project history window closes when trying to apply changes against a database linked to Perforce source control system
• The Object history window closes when trying to apply changes against a database linked to Perforce source control system
• The Action center tab switches from offline to online mode after refreshing even when the option to go offline is not changed
• "Could not find a part of the path < custom_scripts_location > " error is encountered when initiating the Action center tab after shared connections are imported for the shared database
• "Database changes detected. Refresh the "Action center" tab" message is shown after closing the Project history window
• The Browse for folder button for depot does not exist under the System login tab of the Source control setup window for Perforce source control system
• SQL Server Management Studio must be restarted in order for the imported shared connections to take effect when working in the shared model
• "Source control error: Failed commit!" error is encountered after specifying incorrect username when connecting to a public Git repository hosted on BitBucket.org
• The projects under Git branches are not synchronized with branches state when we link a database to a non-master branch
• Check state for listed objects in the Action center tab is not remembered after the Action center tab is refreshed
• Excluded objects are shown in the Object status window
• The "White space" ignore comparison option is checked on the start up
• Commands in the Object Explorer pane context menu are duplicated
• The label name containing spaces is deleted when the OK button is clicked on in the New label window
• The newly added comments to the object script are not shown in the Script difference view
• The object icon in the Object Explorer pane goes grey when the changes are reverted
• "A secure connection could not be established" message is shown when linking for the first time to Git repository hosted on GitHub
• All options are disabled in the Local settings tab of the Options dialog when two or more SQL Servers are connected in the Object Explorer pane
• The action icon in the Action center tab changes direction when objects are checked
• Static data change disappeared from the Action center tab once the table is renamed
• "Database and source control are synchronized. Click to refresh" message is shown when committing changes to source control is stopped
• "Exception caught during execution of push command" error is encountered when committing objects to a Git repository hosted on GitHub without specifying password under the System login tab of the Source control setup window
• The Cancel button inside the progress bar is not working
• "No source control labels found" message is shown when trying to commit change to a repository from the Object Explorer pane
• The Azure DevOps project created in root cannot be deleted from the Choose project window of the Source control setup window
• Clicking the Apply button in case of committing changes takes 3 seconds to respond
• Objects in the Local settings tab of the Options dialog become unchecked when the grouping is cleared
• The information about creating a new database will be initiated in the Source control wizard even when clicking the Previous button in the Development model step
• Database disappears from the database drop down list when trying to choose a database for storing framework objects in the Source control setup window in case a single database exists on a SQL Server
• The Object Explorer pane become unresponsive when right click on a linked database
• Tables without primary keys are shown in the Static data window
• All options are disabled in the Global settings tab of the Options dialog when two or more Servers are connected in the Object Explorer pane
• The add-in should be checking repository availability before the Action center tab is started
• Selecting another database in the Object Explorer pane when the Action center tab is opened unchecks all listed objects in the Action center tab
• All objects are unchecked after the Action center tab is restarted
• Static data changes are not applied when label is applied against a database
• The name of the user who modified table is missing from the Edited by column of the Action center tab
• The Enter keyboard key should do the same action as left mouse click on the Apply button in the Action center tab
• There is not any indication of initializing the Action center tab after refreshing it
• The ApexSQL database disappears from the dropdown list of databases under the Development model tab for the shared model when the dropdown list is clicked on
• The Alt keyboard key should not do the same action as left mouse click on the Next button in the Source control setup window
• The add-in does not allow importing connections for databases that need different credentials from the ones specified first when importing connections for the shared model
• The "Edit" option for uncommitted migration scripts is missing from the Action center tab context menu
• The Migration scripts window does not have a script preview section
• Additional objects linked after linking a database are not detected by the Action center tab

Known limitations:

• "Make sure that correct username and password are specified" message appears when try to link on Git source control system hosted on Bitbucket Server over ssh key authentication

Enhancements:

• New error handling and send logs functionality
• The Renewal support information in the About window now can be refreshed in order to collect the latest information about the support duration

Fixes:

• "Invalid activation code" error is encountered during the add-in activation process when using activation key of an older version of the add-in
• The Repository column in the Action center tab is missing information about the repository state when ApexSQL Diff is installed

Enhancements:

• Support for Team Foundation Server 2018 Update 2
• Support for SQL Server Management Studio 17.8
• Applied concepts of Visual Language Dictionary for Visual Studio for iconography, imagery, colors, menus, fonts, formatting and other GUI elements

Fixes:

• The Action Center tab stays open after the Cancel button is clicked on in the connect to source control window
• "Access denied. Make sure that username and password are correct" error is encountered when accessing the Git repository hosted on Azure DevOps if it is accessed using the AD accounts
• The Object Explorer tree collapses every time an object is unlinked from source control
• The options under the Global object filtering tab are not being saved for SQL Server databases hosted on Azure virtual machine and linked to the Team Foundation Server repository
• "There is nothing to sync between the source control version and the database" message is shown for the shared databases linked to the Subversion repository when the Get button is clicked on
• The Schemas drop down list under the Object filtering tab of the Source control setup window is empty when skipping the Development model tab
• Custom scripts are not shown in the Object filtering tabs of the Options dialog
• "There is nothing to sync between the source control version and the database" message appears when applying changes from source control against a database related to custom scripts
• Excluded custom scripts remain in the Action center tab
• Loading the Action center tab takes too long in case of linking a database using the Working folder option
• The Action center tab show differences after applying changes from the repository against a database
• "There is nothing to sync between the source control version and the database" error is encountered when trying to delete the migration script through the Action center tab
• The WITH NOCHECK part is added before every constraint in a database object script after reverting a static data change in the Action center tab
• The user who renamed a column with the sp_rename procedure will not be listed under the Edited by column in the Action center tab
• SQL Server Management Studio stops working after creating multiple branches one after another
• The previously committed migration script appears in the Action center tab after re-linking a database
• "There is nothing to sync between the source control version and the database" message appears when applying a custom script from source control against a database
• SQL Server Management Studio stops working when filtering SQL schemas or object types under the Global settings tab of the Options dialog
• Including objects under the Global settings tab of the Options dialog will not include the same objects under the Local settings tab of the Options dialog
• The lasted used path for importing connection is not remembered under the Connections tab of the Options dialog
• The add-in takes too much time when browsing the Project history for databases with large number of objects after a number of committed change sets
• The Options dialog closes without any warning even when the Escape button (ESC) is pressed even if there are changes made
• The add-in does not check if the selected default merging tool is installed or not
• "Warn about pending changes on exit?" option does not work unless the Action center tab is opened
• "Column ‘REFERENCE_VALUE’ does not allow nulls. " error is encountered when applying the static data from source control to database
• Only the last linked shared database can be chosen under the Global settings tab of the Options dialog
• The synchronization script is created when applying a label even if there are no differences between a database and created label
• The migration script cannot be edited after it is saved
• The Static data window closes if one of the selected tables does not containing the primary key
• "An error occurred while updating the database object" error is encountered on attempt to undo changes made on a database linked in the dedicated model
• The Action center tab goes online automatically after refreshing even if the ‘’Go offline’’ option is initiated before the refresh
• "Make sure that correct username and password are specified" message appears when linking to a local folder that is not initialized as a Git repository
• "Exception: Serialization failed for Production.ProductDocument [Data].xml" error is encountered when committing static data changes
• The add-in checks credentials for Git public repository
• The Team Foundation Server project cannot be deleted from the Source control setup when the alternate credentials are not used
• Exported object selection cannot be imported unless the ‘’Show all objects’’ button is not initiated under the Object filtering step of the Source control setup
• Only filtered SQL schemas will be shown in the Object filtering tab of the Source control setup after importing object selection with the specific schemas
• The Options dialog cannot be initiated in case multiple ApexSQL tools are integrated in SQL Server Management Studio
• The Action center tab can be initiated for a SQL database that was previously selected even after disconnecting a SQL Server instance from the Object Explorer pane
• "Object reference is not set to an instance of an object" message appears when opening the Options dialog
• "There is nothing to sync between the source control and the database" message is shown when try to get the migration script from the repository
• "Failed to authenticate the Visual Studio Online account" error is encountered when linking a database to a Git repository hosted on Azure DevOps using HTTPS protocol
• The static data cannot be linked from the Action center tab
• The migration script is not shown in the Action center tab
• The Get button is disabled under the Object history window
• The Connect to source control dialog appears each time when the Action center tab is initiated even if a connection to a Team Foundation Server is established using Windows credentials
• "Save changes made against a database DatabaseName" dialog appears when switching between database in the Administration tab of the Options dialog
• The Action center tab does not contain any information after linking a database to an empty repository
• "Incorrect repository path is used for Subversion" message is shown when the "Browse for folder" button is clicked on when linking a database to the repository hosted on the Subversion
• Linking a database to a Perforce repository is possible without entering username and password or even with wrong credentials
• The Activation window is closed without warning when entering the wrong Activation key
• A database cannot be linked to a Mercurial repository hosted on BitBucket.org
• The static data stays in the Action center tab after commit to the repository is performed
• All objects with schema changes stays in the Action center tab after the commit
• The Apply button in the Action center tab does not work
• "The process was terminated due to an unhandled exception." error is encountered when ApexSQL Search 2016.07.0080 is installed and the Analysis Services is clicked on
• The "Send logs" option doesn't work
• "Source control error: Push operation failed..." message is shown when try to link a database to the Mercurial repository hosted on Bitbucket.org
• "Source control error: Push not permitted. Please check if you have write access to the repository" error is encountered when trying to create a new project on the Git repository hosted on BitBucket.org using SSH authentication
• "Detected local offline commits. ApexSQL Source Control must synchronize repositories to go online" message is shown when trying to link to Git repository hosted on BitBucket.org using the SSH authentication
• "File not found: < folder location >" Error is encountered when trying to link a database to the Mercurial repository hosted on BitBucket.org using the SSH authentication
• The user created user and schema objects do not have the add-in context menu commands in the Object Explorer pane

Changes:

• The creation of a new project through the add-in for the Team Foundation Services repository hosted on Azure DevOps is deprecated
• The creation of a new project through the add-in for the Team Foundation Services repository hosted on Team Foundation Services is deprecated
• The application now requires Microsoft .NET Framework 4.7.1
• Support for Windows Vista and Windows Server 2008 is deprecated

Known limitations:

• For linking a database to the Team Foundation Services repository hosted on Azure DevOps the alternative credentials must be used
• For linking a database to the Team Foundation Services repository hosted on Team Foundation Services the alternative credentials must be used
• Creation of the SSH keys through the PuTTYgen for linking a database to the Git repository hosted on BitBucket.org is not supported
• Creation of the SSH keys through the Command Line Interface for linking a database to the Mercurial repository hosted on BitBucket.org is not supported
• Team Foundation Server check-in policies are not supported

Fixes:

• “An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)” message is shown when try to link a database to Perforce source control system
• “There is nothing to sync between the source control version and the database” message is shown when the Get button is clicked on in the Project history window
• Filtering settings done under the Global settings tab of the Options dialog are not remembered
• "Make sure that username and password are correct" error is encountered when linking a database to a Git repository hosted on Azure DevOps hosted by company account using the SSH protocol
• SQL Server Management Studio stops working after connecting to a SQL Server Analysis Services instance
• SQL Server Management Studio stops working after connecting to a SQL Server Reporting Services instance

Fixes:

• A database cannot be linked to a Git repository hosted on company Azure DevOps with Azure AD account when SSO authentication is enabled
• 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
• The add-in only shows Team Foundation Server projects from the Default collection even if a different Collection is selected in the drop-down list in the System login step of the Source control wizard
• A database cannot be linked to a Team Foundation Server repository hosted on Azure DevOps
• The comparison step in the Action center tab works indefinitely when linking a database to a Git repository hosted on Azure DevOps
• Polish static data characters are shown as question marks in the Script view difference window
• SQL Server Management Studio stops responding when a database is already linked with an older version of the add-in in the shared development model
• Memory_optimized tables stay in Action Center tab after the commit

Enhancements:

• Support for Team Foundation Server 2018

Fixes:

• The "Case in name" option under the Script options tab of the Options dialog does not work
• SQL Server Management Studio stops responding when Increase font size to max and turn on the “Word wrap” option in the Differences preview window
• An object appears in the Action center tab after it is committed to the Perforce repository
• "Source control error: Add folder failed with message 'TF14054: The Encoding -2 is not valid. The client should never send this value.'" error is encountered when creating a Team Foundation Server project on root of a repository
• "Source control error: Method not found" error is encountered while creating new project for a Team Foundation Server repository
• ANSI PADDING setting is set to OFF after committing SQL index to a repository even if the SQL index script shows the same setting as ON in SQL Server Management Studio
• Notification for new versions of add-in does not work
• The add-in context menu is missing from the Object Explorer pane
• "The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)" error is encountered when linking a database to a Perforce repository
• "SELECT failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS'." error is encountered when compiling any change on a server where the add-in server DDL trigger is installed
• "An error occurred while updating database objects" error is encountered when the Undo button is clicked in the Action center tab
• The add-in does not generate complete script when applying changes from source control against a database

Fixes:

• "Could not select repository on server 'tfs_server_url'" error is encountered when trying to link a database to a Team Foundation Server repository
• "The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)" error is encountered when linking a database to a Perforce repository
• "The branch field cannot be empty" error is encountered when the Refresh button is clicked under the System login step of the Source control wizard when linking a database to a Git repository
• "Object reference not set to an instance of an object" error is encountered in the Comparison step of the Action center tab when SQL procedures are filtered out
• "Make sure that correct username and password are specified" message is shown when the Finish button is clicked for linking a database to Git or Mercurial using the SSH authentication
• Enter key deletes the specified branch path in the Merge branches dialog
• ANSI PADDING setting is always set to OFF after committing SQL Clustered index to a repository
• "Microsoft SQL Server Management Studio 17 is not installed. Please install this version to integrate into" message is shown and the add-in installation doesn’t continue when SQL Server Management Studio 17.4 is installed

Enhancements:

• Support for Team Foundation Server 2018 RC2

Fixes:

• Changes cannot be committed to a separate Mercurial branch
• The Action center tab shows incorrect scripts for a stored procedure after it is edited when an Azure SQL Database is linked to source control using the Shared model
• "Source control error: Cannot check-in pending changes. The array must contain at least one element. Parameter name: checkinParameters.PendingChanges" error is encountered on initial check-in to Team Foundation Server
• Differences from the selected label are not applied against a database
• Changesets are not shown in the Merge branches dialog when a database is linked to Subversion or Mercurial repository
• "Cannot check-in pending changes 'Could not load file or assembly 'Microsoft.TeamFoundation.WorkItemTracking.Proxy, Version = 14.0.0.0''" error is encountered on an attempt to check-in changes to Team Foundation Server
• "Make sure that correct username and password are specified" message is shown when linking a database to a Team Foundation Server repository hosted on a local machine
• The Action center tab does not load the selected branch after it is picked from the Active branch drop-down list when working with Mercurial
• Options in the update dialog are not saved after SQL Server Management Studio restart
• "Could not load type 'Microsoft.VisualStudio.Services.WebApi.Utilities.Internal.UserAgentUtility" error is encountered when the Browse button under the System login tab of the Source control wizard is clicked for the Team Foundation Server repository
• The add-in does not work with Amazon RDS
• The Merge branches feature does not work for Subversion source control system
• "The type initializer for 'ApexSQL.Common.UI.Forms.MetroMessageUpdater' threw an exception" error is encountered when the Get updates command under the Resources tab is clicked
• Databases linked in the Dedicated model are shown under the Administration tab of the Options dialog
• The Action center tab does not load in SQL Server Management Studio 17 when ApexSQL Generate is installed
• SQL database structure is not committed to a Git local repository that is configured as bare
• "Method not found: 'Void Microsoft.VisualStudio.Services.Common.VssPerformanceEventSource.RESTStart(System.String)'." error is encountered when creating a Team Foundation Server project in the repository root with alternate credentials specified
• "Object reference not set to an instance of an object" error is encountered when trying to link a database to a Team Foundation Server project that does not exist
• "Error while trying to format the server name from: IP_address\SQLServer_instance: No such host is known" error is encountered when connecting a SQL Server from a remote machine using the IP address
• The Close button (X) saves the changes made under the Development tab when Shared model is used instead of just closing the modal dialog
• "TF200016: The following project does not exist" error is encountered when creating a Team Foundation Server project using the add-in wizard while if alternate authentication credentials are not specified
• "Object reference not set to an instance of an object" error is encountered when specifying a value that is not in the allowed range for the changeset ID under the Filter row in the Project history dialog
• The add-in does not work on Git repository when using the Azure DevOps account
• The action item in the Action center tab will be switched on right click
• The White space ignore comparison option under the Script options tab of the Options dialog doesn’t work

Enhancements:

• Performance improved when working with databases connected over narrowband (less than 6Mbit/s):
  • The Object Explorer context menu opens up by up to 1,000% faster
  • The Source control setup wizard opens up by up to 500% faster
  • The Options dialog opens up by up to 1,185% faster
  • Filtering individual objects for shared databases has been sped up by up to 1,000%
  • Filtering schemas and object types for shared databases has been sped up by up to 200%
• GUI themes:
  • Light
  • Blue
• Support for SQL Server 2017 RC2

Fixes:

• "Database and source control are synced. Click to refresh" message appears in the Action center tab even if there are changes in the Perforce depot
• The add-in selects a random Team Foundation Server collection when linking a database if a collection is not already specified in the repository URL
• The Object filtering selection can be exported even if a database is not selected in the Object filtering tab of the Options dialog
• Team Foundation Server projects created from the add-in wizard are not visible in the Team Foundation Server
• "Object_Filtering<server_name_database_name>.xml Path does not exist. Check the path and try again" error is encountered upon exporting object selection when the SQL Server name contains a backslash character
• "Passphrase is empty or invalid" error is encountered when linking a database to a Git repository using the SSH protocol
• "Value does not fall within the expected range" error is encountered when linking a database to a Subversion repository when using the Windows integrated authentication or when the username is not specified
• "URL 'local_path' non-existent in revision 2" error is encountered when trying to browse a Subversion repository from the System login step of the Source control wizard when the non-existent project is specified in the Project field
• "Select a database in order to export/import object selection" message is shown in the Object filtering tab of the Source control wizard when linking a database
• The "Apply policies" option of the Options dialog is not enabled when the Check-in policies active option of the Source control setup wizard is enabled
• "Connection failed with message 'abort: no suitable response from remote hg'" error is encountered when linking a database to a Mercurial repository hosted on Bitbucket.org when using the SSH protocol
• The "Apply policies" setting under the General tab of the Options dialog will not be saved after the Options dialog is closed
• The "Check for updates on startup" and the "Show patches" options are missing in the ApexSQL Source Control available updates window
• Get from repository action is not set by default in the Action center tab when the Apply all from source control command is used from the Object Explorer context menu
• "Exception of type 'System.OutOfMemoryException' was thrown" error is encountered when committing static data for specific databases
• "Failed commit! Error The executable did not complete within the allotted time" error is encountered when committing static data for more than 100 tables to a Mercurial repository
• Pre-defined file format is missing for External options file under the Connections tab of the Options dialog
• "Failed to connect to server" error is encountered when linking a database on a remote SQL Server instance using correct mixed mode authentication credentials in specific cases
• Differences are shown in the Action center tab after applying all changes from source control repository to database if two or more databases with the same compatibility level but located on different versions of SQL Server are linked to the same source control repository in a dedicated development model
• The Action center tab stuck on the third step when comparing objects between source control and database
• "There is nothing to sync between the source control version and the database" error is encountered when applying changes from source control to a database for objects with previously created migration scripts
• "Cannot create branch. Source control error: create branch operation failed with message Exception caught during execution of push command" error when trying to create a Git branch
• "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible" error is encountered when linking a database on a remote SQL Server instance connected using an IP address
• "Parse error: [Incorrect syntax near ','] at [position: 223, line: 14, column: 44]" error is encountered when applying changes from source control to a database
• Schema prefix is included in the synchronization script when applying changes from source control even if the Manage owners option under the Script options tab of the Options dialog is unchecked
• "Unable to locate Mercurial version number in 'Mercurial Distributed SCM (version 4.2 + 4)'" error is encountered when linking a database to a Mercurial repository if the Mercurial client version on a local machine is 4.2
• Static data remains in the Action center tab after it is committed

Changes:

• CLI source control connection type has been deprecated
• Pre-defined XML file format for External options file under the Connections tab of the Options dialog is added

Enhancements:

• Associate Team Foundation Server work item with a committed changeset
• Team Foundation Server check-in policy
• Create and merge branches

Fixes:

• The Action center tab does not display differences when a column is renamed
• The Defaults button in the add-in option does not reset the Show warning for changing policies in the Administration tab option
• An object will be shown like it is locked by someone else when it is locked, edited and the change is reverted
• Object filtering in the Repository only tab in the add-in options can be performed only for the schemas and object types that exists in a selected database
• Filtering in the Object type drop down list is not available for the Database tab in the add-in options under the Object filtering tab
• The Options form closes upon importing object selection in the Object filtering step when a database is not previously selected from the drop-down list
• Missing informative message that the object selection is exported successfully
• Missing option to navigate to the location where the object selection is exported
• Object excluded in the Global settings tab for one database will be automatically excluded for all other database where the object with the same name exists
• Selecting a database in the global settings is not synchronized with the local settings
• The Action center tab does not inform the user that custom scripts are added after the Options form is closed upon adding a custom scripts folder path
• Schema name is not scripted in the Action center tab for the specific SQL database objects
• The Browse button for the Custom scripts path cannot be used even if the correct path is specified
• The Options form closes when selecting a database from the drop down list in the Local filtering tab
• Connecting to the same SQL Server instance using different connection string shows previously linked databases as unlinked
• The user who excluded objects globally is not shown in the Excluded objects table
• An object that was linked before it is excluded in the Global settings tab becomes unlinked after it is included back
• "An exception occurred while executing a Transact-SQL statement or batch" error is encountered on expanding the Tables node when a database is linked to SQL Server 2017
• "'System.Collections.Generic.List`1 System.Guid" error is encountered in Visual Studio Team Explorer 2015 when the add-in installed
• "Cannot set LocalPath. Method not found:SystemCollections.Generic.IEnumerable" error is encountered when linking the second database to a Team Foundation Server repository on a SQL Server instance where one database is already linked
• The add-in fails to link a database when specific characters are used as a username
• SQL database object is not recognized as linked if it contains the '&' character in its name
• "Could not load file or assembly 'Microsoft.SqlServer.Types, Version=12.0.0.0'" error is encountered when applying the static data
• "Could not load file or assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=14.0.0.0" error is encountered when committing objects to a Team Foundation Server 2015
• "System.ArgumentOutOfRangeException. Length cannot be less than zero." error is encountered when the Link database to source control option is clicked from the Object Explorer context menu
• Object status form shows incorrect user that performed a check out or lock operation on an object when previously accessing SQL Server as a different user and performing a check out or lock operations
• "Cannot check in pending changes. The array must contain at least one element" error is encountered when committing the static data to source control

Enhancements:

• Support for Git source control system hosted on Azure DevOps
• Support for Bitbucket in an Active Directory
• Script difference panel options:
  • Change colors
  • Increase/Decrease font size
  • Find
  • Word wrap

Fixes:

• "Item <item_name> is obsoleted. Root.Find() must be used to get actual item" error is encountered when creating a sub-folder in the Azure DevOps repository
• SQL object types included in the add-in options after the database is already linked will not appear in the Action center tab
• Differences are not shown consistently when the Show different rows only option is checked
• New Team Foundation Server project cannot be created through the add-in wizard when using Team Foundation Server 2015 or Team Foundation Server 2017
• The information about SQL users is shown in the Object status window after applying changes to a database even when the status of the object is unchanged
• Change sets are inconsistently ordered in the Project history dialog
• Warning message in the System login step of the source control wizard is not focused when a non-existing project name is specified for the Git repository
• Differences between source control and database version of a SQL table are not highlighted correctly in the Differences section when a not null constraint is added
• The add-in generates different SQL scripts when applying a change through the Action center tab and through the Project history dialog
• Action center tab SQL script differences are highlighted on one side only when a column is renamed
• Missing informative message in the Action center tab when changes are detected after including/excluding SQL schemas from the Object filtering tab in the add-in options
• Database change log dialog filter finds only records that start with the specified filter value
• Username and password fields are mandatory in the System login step of the source control wizard when linking a database to a local repository
• The Action center toolbar command refreshes the Action center tab only if the Action center tab is active
• Inappropriate differences are highlighted in the Action center tab when differences are detected for the custom scripts
• "Database changes detected. Refresh the "Action center" tab" message appears in the Action center tab after closing the Options form even when no database changes were made
• Schema field combo box filter is missing in the Database section under the Object filtering tab
• Key column filtering does not work in the Static data dialog
• Static data dialog filter row works only for values that starts with the specified value
• The Migration scripts window is displayed even when there are no migration scripts specified
• "Database changes detected. Refresh the "Action center" tab" message appears when changing the Enable committing other users changes option
• "Parsing error: Incorrect syntax near 'COMPRESS_ALL_ROW_GROUPS'" error is encountered when applying a change that adds a dropped column from source control to the database
• "Object reference not set to an instance of an object" error is encountered when applying specific changes from source control to database after changing the script option settings
• "Object reference not set to an instance of an object" error is encountered when committing a deletion of a SQL database user that contains a dot in its name
• "There was a conflict while trying to commit" error is encountered when committing a change made by another user using the shared model
• The Ignore comments option does not work
• The Ignore Lock_Escalation option does not work
• The Ignore white spaces option does not work
• "Invalid object name dbo.ApexSQL_SC_ObjectsTable" error is encountered when using the keyboard shortcut for the Object status form while a database in the Object Explorer pane is linked using the dedicated model
• "The link to source control is removed" error is encountered when using the keyboard shortcut for the Static data form in case any object is highlighted in the Object Explorer pane
• The Go offline setting will reset upon restarting SQL Server Management Studio
• The Project history dialog shows incorrect list of committed changes when multiple databases are linked to the same Subversion repository
• The Object filtering step in the source control wizard does not export/import object selection settings properly
• Running instance of the SQL Server Management Studio stops working when installing the add-in
• The add-in Object Explorer context menu commands are disabled until clicking on another Object Explorer node and clicking back
• "Cannot drop database "ApexSQL_SourceControl" because it is currently in use." error is encountered when linking a SQL Server 2005 database
• The add-in fails to apply static data changes if the identity column of a SQL table in source control is different from the database version
• Execution results cannot be copied from the Script execution results window after trying to apply changes from source control to the database
• "Cannot open database 'database_name' requested by the login. The login failed" error is encountered when the add-in database is deleted while at least one database is still linked using the shared model
• Changing the SQL column from null to not null will not be detected as a change by the add-in
• The Initializing progress bar remains open after applying changes using the alternative synchronization engine activated from the add-in options
• The Apply button is disabled after filtering objects in the Action center tab
• "Cannot open database 'database_name' requested by the login. The login failed" error is encountered after the add-in is updated
• "Invalid object name 'information_schema.schemata'." error when linking a SQL Server 2005 database
• "There are uncommitted changes in some of the linked databases. Exit anyway?" message appears twice when closing the SQL Server Management Studio
• A conflict occurs in the shared model when checking out and checking in an object edited by another user
• "Commit failed. Check log file for more details" error is encountered when committing the static data for a SQL Server 2005 database
• The progress bar where the add-in is checking if a database is offline, before initiating the source control wizard, works indefinitely when the currently connected SQL user does not have sufficient permissions for the database
• The information about minimal permissions required for the shared model in the source control wizard is not correct when no databases are linked
• Capitalization differences in SQL schema name are not ignored in the Action center tab
• "An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name." error is encountered when linking a SQL Server 2008 R2 database
• "Table 'table_name' not found" error is encountered when applying changes from source control to the database when the synchronization script includes dependent objects that are not a part of the source control
• "SELECT failed because the following SET options have incorrect settings: 'ANSI_PADDING'." error is encountered when modifying any SQL database object while the add-in DDL trigger is present on the server
• Linked database can be specified as a database to host framework objects by typing its name in the Database field when linking a database using the shared model
• "Cannot access destination table 'table_name'." error is encountered when applying static data from source control to the database
• Custom scripts remain in the Action center tab after committing to source control
• Differences for the committed custom script are shown in the Action center tab after the initial commit
• The Warning about pending changes on exit option does not work
• The Action center tab is not refreshed after switching between linked databases in the Object Explorer pane and then using the Action center toolbar command
• Migration script item will be duplicated in the Action center tab each time only the migration script is applied from source control to a database
• "Object Schema [guest] is ignored: object already exists." error is encountered when applying schema changes from source control to the database after upgrading from the previous version of the add-in
• Team Foundation Server project created inside the repository cannot be deleted through the add-in wizard
• The Migration scripts feature doesn't work when applying changes from source control to the database
• SQL Server Management Studio stops responding after applying large amount of static data from source control to the database
• "The user does not have sufficient permissions to link databases as shared" error is encountered when using the Import connections feature in the shared model
• "Invalid object name 'ApexSQL_SourceControl.UserMappings'" error is encountered when linking the second database in the shared model on SQL Server 2008 or SQL Server 2008 R2
• "Test succeeded" message appears when testing the SSH connection with the URL that is generated for the HTTP connection when linking a database to a Git repository
• "Source control error: Failed commit! Error Exception caught during execution of push command" error is encountered when committing changes to a Git repository when the HTTP URL is specified instead of SSH
• "Database is already linked in the dedicated model" message appears when trying to link a database using the shared model from another location after it is already linked using the shared model
• "Source control error: Provided local path doesn't exist" error is encountered when trying to get a specific version of an object from the source control history
• The Project history dialog closes when trying to apply changes when the linked Subversion project is nested
• Progress bar when applying changes from source control to database is not working correctly
• Static data is not visible in the source control history after it is committed to the source control
• "Enter description" message appears in the Migration scripts dialog even though the description cannot be added like this
• "Object reference not set to an instance of an object" error is encountered when changing the add-in options while the linked database is not selected in the Object Explorer pane
• "Cannot set local path: Method not found" error is encountered when linking a database from the same SQL Server instance to the Team Foundation Server repository where another database is already linked

Changes:

• Support for SQL Server Management Studio 2008 and SQL Server Management Studio 2008 R2 integration has been deprecated
• The add-in now requires Microsoft .NET framework 4.5

Enhancements:

• SQL Server vNext CTP1 support
• Team Foundation Server 2017 support
• Progress bar indicator is now available when checking permissions level for a database that is selected to be linked to source control

Fixes:

• "Failed to connect to server 'server_name'." error is encountered when linking the first database on a server, in case the user does not have the CONTROL SERVER permission
• SQL script comment containing the information about the static data is in a single line in the "Get changes" form when applying the static data for more than one table

Enhancements:

• Significant improvements in the shared SQL source control development model implementation
• SQL Server Management Studio v17.0 RC1 integration
• Global object filtering
• An option to manage number of changesets shown in the history
• An option to manage number of labels shown in the “Labels” form

Fixes:

• The add-in cannot manipulate with Indexes as separate object types
• "An error occurred while adding a new label" error message is encountered when naming a label with spaces between words for Git repository
• Checking the history while in the offline mode is active does not work in some cases
• SQL Server Management Studio stopped working when disconnecting Analysis services
• "Cannot access destination table 'ApexSQL_SC_ObjectsTable'." error when connecting to SQL Server 2005 from SQL Server Management Studio 2014
• The add-in does not accept the '/' character in the branch name
• Shortcuts are not working in SQL Server Management Studio 2016
• "There was a conflict while trying to commit" error appears when trying to commit the change in shared model
• The "Database change log" form does not show rename operations
• A non-intuitive message is shown when starting SQL Server Management Studio, in case the password for the repository must be specified
• "Database changes detected" message is shown when unlinking a single object from the Object Explorer pane
• Database cannot be linked to a subfolder when linking to the Subversion repository
• Changing the location of the intermediary folder does not move any data to the specified folder
• SQL Azure database cannot be linked using the shared model
• The user can link a database with insufficient permissions, although there will be no objects shown in the "Action center" tab
• User defined data types are not properly tracked by the "Action center" tab
• "Object reference not set to an instance of an object" error appears when changing the ANSI option
• Multiple indexes cannot be rebuilt by a running procedure while the Permissive policy is enabled
• Creating of new projects from the Source control setup wizard for the latest version of Mercurial source control system 3.9 and above is not working in some cases
• Wrong information message is shown when switching from one database to another in the “Object explorer” pane
• Migration script is shown in the “Action center” tab as a difference even after it is committed to the repository
• "Database and source control repository are synced" message appears after executing the script to alter specific objects in a database
• The FILLFACTOR is missing for a table in the Script difference view pane of the “Action center” tab, even after executing the specific script that creates it
• System login credentials are not remembered for the same source control system, in some cases, when switching from the Dedicated to the Shared model
• "Permissive policy is enabled on this database. Object ‘object_name’ must be checked out before editing" error is encountered when an object is unlinked and dropped from a database
• A specific object is shown as static data in the “Action center” tab, after changing its structure
• Undoing the check out operation with the “Get latest” option will be prevented if the Permissive policy is enabled
• The "Edited by" column can be edited in the "Action center" tab
• Inappropriate message when changes made by other users cannot be committed
• Clicking the “Defaults” button in the add-in options will restart the script options settings to the inappropriate state
• "Some framework objects are not created successfully" error is encountered when putting framework objects in a single database
• The "Offline" mode does not work in some cases
• "The server principal 'user_name' is not able to access the database "database_name" under the current security context." error when making a change on a database
• "Invalid object name 'containedDb.sys.database_principals'" error is encountered when trying to manually drop the add-in DDL trigger
• The "Object status" form does not show objects for other databases, if more than one database from the same SQL Server is linked
• "Unable to connect to a repository at URL 'file:///C:/Repo/Subversion9'" error is encountered when trying to link a database to Subversion repository
• "Invalid object name 'ApexSQL_SC_UsersMappings'" error is encountered when linking a database in the dedicated model
• "Unable to cast object of type 'System.Int32' to type 'System.String'" when linking a database to a Git or Subversion repository
• The add in database will be removed after the last user unlinks a database
• The "Action center" tab cannot commit any objects on TFS, when working in the shared model
• Changes made in the "Local filtering" tab will not be saved after closing the "Options" form
• SQL Server Management Studio closes when creating a new TFS project through the add-in wizard
• The add-in shows all objects in the "Action center" tab, after the initial commit, with false differences
• DatabaseSettings.xml file is empty when linking a database to a working folder
• The "Action center" tab goes offline upon SQL Server Management Studio restart, in case the repository password is not saved during the linking process
• Object filtering on a local level overrides the global filtering upon opening the add-in options form
• An incorrect message is created when an existing database is used for framework objects
• "Edited by" is not being logged, in some cases, when changes to an object are made
• Objects are displayed in the "Object filtering" tab, even when the "Uncheck all" option is used
• ApexSQL Source Control trigger is not created in SQL Server Management Studio 2008 R2 when using the shared model
• "Must declare the scalar variable "@username"." error is sometimes encountered when linking a database in the shared model
• The add-in fails to integrate in SQL Server Management Studio 2008 in some circumstances
• The add-in trigger is not created when linking a database in the shared model hosted on SQL Server 2008

Enhancements:

• Support for SQL Server on Amazon RDS
• New Script options tab in the Options window:
  • Ignore comparison options
  • Synchronization options
  • Manage owners options
• Improved Import connections feature:
  • New Connections tab in the Options window
  • New pane for choosing databases that will be linked

Fixes:

• Created nested projects are shown as a root for the Subversion repository
• Changing the location of the working copy will impact only databases that are linked after the change
• The "ApexSQL_SC_DatabaseLog" table is not ignored when linking Azure SQL Database using the dedicated model
• The add-in keeps asking for the password upon initiating the Action center, although it does not require any credentials when connecting to a local Mercurial repository
• "Some ApexSQL Source Control framework objects were not created successfully" error is encountered when linking an Azure SQL Database
• The Project history shows the "Initializing" progress bar when the first commit is selected in the project history form, even if the form itself is fully loaded
• The created SQL assembly is shown as object type "All" in the "Object status" form
• “Failed to create a database for checking a validation of migration scripts” error is encountered when trying to apply a change that contains a migration script
• The user is not properly shown in the History forms when working with migration scripts on Team Foundation Server
• Locally deleted migration script cannot be reverted through the "Action center" tab, after deleting from the "Migration scripts" form
• New Team Foundation Server project fails to appear after it is created through the Source control setup wizard in the Project form
• Static data is not shown in the same way across all source control systems
• “An error occurred while adding a new label” error message is encountered when naming a label with spaces between words for Git repository
• Setting up the comment will not affect the Action center if it is opened
• Specific objects cannot be excluded from being version controlled
• “Object reference not set to an instance of an object” error is encountered when committing specific changes to a Git repository
• The add-in’s DDL trigger remains enabled when applying changes from the repository using the Shared model
• The add-in throws an error when applying changes for the specific user that exists on the repository only
• No scripts are shown in the "Differences" section of the "Action center" tab for files that have specific line feed settings
• “[Line 1, Column: 3] Incorrect syntax near \” error is encountered when applying changes using the alternative synchronization engine
• The "External data sources" are not supported as object type
• Excluded schema is shown in the Action center tab
• An error is encountered when applying changes when a schema is excluded from being version controlled
• The "Automatically check for updates on application startup" option does not work
• SQL script of the specific object will not be shown in the "Differences" section of the "Action center" tab
• ”User 'user name' is currently linking the same database” message is encountered after the initial user is back to the first step of the wizard
• SQL Server Management Studio stops working when the framework objects are missing for the linked database
• The add-in does not accept the '/' character in the branch name
• “Some ApexSQL Source Control framework objects were not created successfully” error is encountered after relinking a database
• Specific SQL indexes are not scripted properly to the source control repository
• False differences are shown when linking a database populated by the other ApexSQL tool
• Scripting inconsistencies are encountered when working with the repository populated by ApexSQL Diff
• The "ON PRIMARY" is not properly scripted when working with SQL Server 2008 database
• The control file is not equivalent to the one created by ApexSQL Diff
• The script compatibility level for SQL Server 2008 and SQL Server 2008 R2 have inappropriate values specified
• Executed SQL script for the stored procedure will not be shown in the "Differences" section
• “Database changes detected. Refresh the Action center tab" message appears after closing the "Project history" form
• “The user does not have sufficient rights to link this database” warning appears when a database contains dot in its name
• “An error occurred while updating the database object” error is encountered when pulling the custom script from the "Project history" form
• “Parsing errors: Parse error: [Incorrect syntax near '('] at [position: 1500, line: 26, column: 64]” error is encountered when applying stored procedure against a database
• “Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression” error is encountered when editing an object in the Shared model
• The add-in does not recognize the file protocol used for the repository path and it keeps asking for credentials
• "System.OutOfMemoryException" error is encountered when a system table contains excessive data for the Dedicated model
• “Source control error: Failed to get project ID, check log for more details” error is encountered when deleting a project through the source control wizard
• The “Data types” drop-down list is available in the "Object filtering" tab, even if there is no linked database
• Initiating the Migration script twice for the same change does not open the same tab
• The "New label" form closes after the warning message, in case the label is not properly specified

Changes:

• The Import connections feature is moved from the General tab to the new Connections tab

Known issues:

• New project under the Mercurial repository, cannot be created from the Source control wizard on Mercurial version 3.9.1 and above

Enhancements:

• Support for SQL Server 2016
• Support for SQL Server Management Studio 2016 integration

Fixes:

• SQL Server Management Studio stopped working when disconnecting Analysis services
• Excessive message appears requiring a comment when applying a change against a database
• "Database Settings from SC wasn't loaded" error appears when the "Script dependencies" option is checked
• "Value cannot be null" error is encountered when applying an object that does not exist in a database
• "Error while trying to retrieve scripts for ApexSQL Source Control framework objects! : String cannot have zero length." error when linking a database
• SQL Server Management Studio hang when installing the 2016 R2 release of the add-in
• "Could not load file or assembly 'Newtonsoft.Json'" error is encountered upon the initial commit using Git dedicated model
• Changes made against DML triggers are not shown in the "Action center" tab
• Database objects are missing from the add-in framework table
• The "Active branch" drop down list is not refreshed along with the "Action center" tab
• The add-in prevents editing an object while the Restrictive policy is set, even if the object is locked
• Parsing errors encountered when applying changes against a database using SQL Server Management Studio 2016
• TFS workspace will be removed after linking the second database to a new subproject in case another database is linked to a subproject of the same parent folder in TFS
• DatabaseSettings.xml file contains inappropriate information for the SQL database compatibility level
• "This Sql Transaction has completed; it is no longer usable." error appears when linking a database hosed by SQL Server that has the limited bandwidth
• The add-in fails to create framework objects when linking a database to a SQL Server with limited bandwidth
• The filter row in the "Object filtering" tab is not working properly
• "There are no committed changesets. Project history will be available after the first commit" message appears after the first commit on a local Perforce depot
• Timestamp for the committed changesets is at correct when working with Subversion repository
• Custom scripts path reported as not found when it is stored in a nested folder inside the custom scripts root folder
• SQL script of the object is not refreshed in the "Object history" form after the change is applied
• Changes cannot be applied from the history when working with Mercurial source control system
• "Length cannot be less than zero. Parameter name: length" error is encountered when clicking the filter row in the "Project history" form
• "Could not find the xml file" error is encountered when applying static data from the "Action center" tab
• SQL Server Management Studio freeze when committing static data after the initial commit

Known issues:

• TFS projects cannot be created on the root repository if TFS 2015 is used

Enhancements:

• Migration scripts
• Basic Git branching support

Fixes:

• Objects will remain highlighted in the "Action center" tab, on attempt to commit without specifying comment
• "Connection failed: Repository is not empty" error is encountered when browsing folders on the SVN repository
• Inappropriate dialog appears when a database linked to the Git repository is offline and changes are committed
• The "Test" button is missing when getting back from the "System login" step to the "System selection" step, in case the "CLI" or the "Working folder" options are initially selected
• The add-in cannot work with an empty file stored in the custom scripts folder
• The "Action center" tab allows static data for only one table to be linked in case the data exists on the repository, but it is not linked in a database
• Filtering objects from Object Explorer causes SQL Server Management Studio to be unresponsive
• Inconsistency with the "Project history" and the "Object history" form when there are no commits made by the user
• The add-in shows the test failed message even when the user selected the correct folder path in the TFS repository, when linking a database
• Database will go offline upon double-clicking the "Action center" command in the SQL Server Management Studio toolbar
• Missing informative message in the "Action center" tab that database changes are detected after unlinking the static data
• Missing informative message in the "Action center" tab that database changes are detected when adding or removing a custom scripts folder from the add-in options
• "Database changes detected" message appears in the "Action center" tab even if there are no changes
• "Database changes detected" message appears when refreshing the "Action center" tab after editing an object
• "Database changes detected" message stays active in the "Action center" tab, after the changes are applied within the Object Explorer right click menu
• Excessive message when test for the repository connection fails
• Custom scripts cannot be filtered from the "Repository only" tab, in the add-in options
• An empty workspace on TFS will be created upon clicking the "Test" button in the source control wizard
• "Could not load part of the path" error is encountered when linking a database to localhost
• Connection timeout is missing when trying to connect to Git repository using SSH protocol
• The "Action center" tab stuck at step 1, after connecting to a Git repository hosted by CentOS using the SSH protocol
• Creating labels causing the inappropriate structure in the AppData folder and performance impact when using SVN
• Changing indexes will be presented in the "Object status" form showing incorrect icon
• "Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), non-FILESTREAM varbinary(max), xml or large CLR type columns" error is encountered when applying changes
• Objects are checked out as a different user and the current user cannot access them in case of using specific connection configuration
• Changes from the repository cannot be applied in case the commit was from one version of SQL Server, and the apply process is performed against a database on another version of SQL Server
• "SELECT failed because the following SET options have incorrect settings" error is encountered when trying to delete modified object in SQL Server Management Studio 2008 R2
• SQL Server Management Studio becomes unresponsive when trying to delete empty custom script file
• When unlinking one database from TFS repository, another one, linked to the same repository/project will be unlinked automatically
• "Could not find a part of the path" error is encountered when linking one database to a repository where another database is already linked
• "Object reference not set to an instance of an object" error is encountered when refreshing the AC after creating a label in SVN
• "Source control error: The string must have at least one character. Parameter name: localitem" error is encountered when trying to delete a custom script from the repository
• Changes for SQL table are not properly applied in specific case
• "Object reference not set to an instance of an object" error is encountered when applying static data changes
• "Could not load file or assembly "p4api.net" error is encountered when connecting to Perforce repository
• The add-in shows false differences when committing changes from databases of different compatibility level hosted on different SQL Server versions
• SQL Server Management Studio becomes unresponsive when trying to apply a label
• Differences will disappear when using the "CTRL + A" keyboard shortcut to select entire script in the differences section of the "Action center" tab
• A check-out remains as an object state if an object is edited, after it's checked out, edited, and checked-in
• Missing warning message when applying static data changes only, in case an object change is in the list of changes
• Static data remains in the "Action center" tab, even if the related table is dropped
• An object change remains in the "Action center" tab after it is committed from within the Object Explorer without any messages about committed changes
• "Source control error: Commit failed Changes will not be applied" error when committing changes to a depot on Perforce
• Applying changes is stuck at the "Completed" step when applying static data change from the repository
• "Out of memory exception" error is encountered when making a change that affects all rows when showing the static data differences, in case a table contains a large amount of data
• SQL Server Management Studio stops working when the large script with the static data is shown in the "Action center" tab along with a DDL change
• The add-in cannot compare static data changes from within the "Project history" form
• "Out of memory" error is encountered when comparing between changesets with static data
• Cannot apply static data changes from the "Project history" form
• The "Action center" tab shows differences for SQL custom scripts even if there are no differences

Known issues:

• TFS projects cannot be created on the root repository if TFS 2015 is used

Enhancements:

• Team Foundation Server 2015 support
• SQL Server 2016 CTP3 support
• SQL Server Management Studio CTP3 integration
• Azure SQL Database V12 support
• CLI support for major source control systems
• Support for source control of custom scripts

Fixes:

• Geometry object type will not be written as it should in XML which result data loss
• The upgrade to a newer version is available even after the trial is expired
• Object list in the "Action center" tab cannot be filtered in a way to show only objects edited by the current user
• Wrong default action will be set if linking an empty database to the non-empty repository, when using the shared model
• The filter in the "Action center" tab blocks the entire tab, if another database with applied filter is unlinked
• There is no indication about the end of the process in the Applying changes to database process
• The add-in overwrites the data about the first linked database after the second one is linked, in case of linking two databases with the same name from two SQL Server named instances with the same name
• Changes made by other users can be applied even when an object is locked in case of applying changes from the repository to the database
• Object icon in the "Object Explorer" pane is set as edited after applying a label or the "Get" operation from history
• Missing progress bar after the "Finish" button in the wizard is clicked, and before the "Action center" tab appears
• The database drop-down list for the shared model, in the "Source control" wizard cannot be initiated in a single attempt
• The add-in can be installed even if there are no any SQL Server Management Studio instances presented
• The "Delete" button in the "Choose project" form of the "Source control" wizard closes the form and fails to delete selected project
• Copy functionality does not work in the "Script execution results" form
• Excessive command in the right click menu of the "Script execution results" form
• "Current thread must be set to single thread apartment (STA) mode before OLE calls can be made." error is encountered when copy-pasting the current error in the "Script execution results" form
• "Unexpected error" message is shown when changes cannot be applied from the repository to a database
• Databases are not alphabetically sorted in the drop-down list for the shared model, in the "Source control" wizard
• Inappropriate informative message when trying to create a sub-folder in the root of the TFS repository, when linking the database to source control
• Inconsistency between the message in the "Action center" tab and the "Working offline" option
• The size of the "Differences" section decreases when clicking the "Next/Previous 10,000 lines" command
• Missing option to filter type and action in the "Project history" form
• Inconsistent behavior in the "Action center" tab related to number of checked and selected objects
• "An exception occurred while executing a Transact-SQL statement or batch" error is encountered when the user does not have sufficient permissions to link a database
• "Some ApexSQL Source Control framework objects were not created successfully" error is encountered when the user does not have the "db_owner" database role membership
• Missing informative message in the "Action center" tab that it needs to be refreshed, when linking the static data
• If an object has the same name in different databases on the same SQL Server, the add-in will update status of the object incorrectly
• Status bar shows incomplete information for the Mercurial repository, when the project is nested
• Inconsistent messages when linking the static data from the "Object Explorer" pane and the "Static data" form, if a table does not have a primary key
• Table icon will be shown in the "Object history" form for the "Static data" commit
• Initial commit is not allowed from the Object Explorer pane
• Missing option to manipulate with multiple items in the "Static data" form
• Objects will remain highlighted in the "Action center" tab, on attempt to commit without specifying comment
• The database will go offline if the sub-folder is used for SVN and the label is created
• SQL Server Management Studio becomes unresponsive if objects are filtered in the add-in options
• The add-in fails to integrate in SQL Server Management Studio if SQL Server is 32bit, and the operating system is 64bit
• "Connection failed: Repository is not empty" error is encountered when browsing the folders on the SVN repository
• "Failed to update framework" error appears on each click in the "Object Explorer" pane
• The changes will be committed even if the user cancel the commit process
• "Source control error: Applying changes to working copy failed" error when cancelling the commit process twice in a row
• Missing option to save the password when prompted for repository credentials
• "Database changes detected" message appears when refreshing the "Action center" tab after editing an object
• There is no message in the "Action center" tab about changes detected, if the new object is created, nor the icon in the Object Explorer will be updated
• Changes can be committed if the node in the "Object Explorer" pane is changed without checking the object in the "Object selection" section of the "Action center" tab
• Differences will disappear if the CTRL +A is used while the cursor is in the "Comment" field of the "Action center" tab
• "There is nothing to sync" message appears when applying changes from the repository against the database for the SQL Fulltext stoplists
• Missing informative message that there are changes detected in the database when the static data is linked/unlinked
• The zip file for the static data will not be committed when committing the static data
• Initiating the "Project history" form will switch the focus to another application
• The project on TFS repository cannot be created within the add-in wizard
• Excessive space in the "T-SQL script" preview section of the "Change log" form when adding a column
• The "Changes log" form will not show all changes properly
• The add-in menu is missing from the Object Explorer right click menu, if the language environment is not default
• "Cannot check in pending changes "The array must contain at least one element" error is encountered when unlinking and linking back again a database to TFS using shared model
• The "Working folder" functionality does not work
• "Object reference not set to an instance of an object." error is encountered when initiating the "Action center" keyboard shortcut
• "Runtime error (at 89-1940): Internal error: Cannot access 64-bit registry keys on this version of Windows." error is encountered when installing the add-in on 32-bit operating system
• The "Source control" wizard will not be closed and the linking process cannot be continued after clicking the "Finish" button if the Subversion source control system is selected
• Database will switch to offline mode automatically after connecting to the Git repository if the project is created inside the repository
• When the "Action center" tab is initiated upon linking a database, it will show the "Working offline" button, if another database already linked is in the offline mode
• The "Apply changes to database" form appears when committing objects and cancelling the process
• T-SQL script cannot be copied from the "Apply changes" preview section

Known issues:

• TFS projects cannot be created on the root repository if TFS 2015 is used

Enhancements:

• An option to import connections from external options file is added

Fixes:

• "Failed to update framework" error is encountered on each click in the Object Explorer pane
• The add-in fails to integrate in the host application if SQL Server is 32bit, and the operating system is 64bit
• The add-in menu is missing from the Object Explorer right click menu, if the language environment is not default
• "Cannot check in pending changes "The aray must contain at least one element" error is encountered when unlinking and linking back again a database to TFS using shared model
• The "Source control" wizard will not close when clicking the "Finish" button if the "Working folder" is selected from the source control systems drop down list
• Database will to offline mode automatically after connecting to the Git repository if the project folder is created
• The "Source control" wizard will not be closed and the linking process cannot be continued after clicking the "Finish" button if the Subversion source control system is selected
• "Runtime error (at 89-1940): Internal error: Cannot access 64-bit registry keys on this version of Windows." error when installing the add-in on 32-bit operating system

Enhancements:

• The "Working folder" option is added for both dedicated and shared development model
• An option to Check-in/Commit changes through the Object Explorer is added
• An option to Link/Unlink object from the Object Explorer is added
• An option to filter objects that exists only on the repository is added
• An option to add a directory to repository root for Git and Mercurial is added
• An option to delete static data from the repository is added
• An option to see if someone else linked static data and link it from the "Action center" tab is added

Fixes:

• The add-in fails to recognize proper version of SQL Server Management Studio if Cumulative update 7 is installed
• The "Database change log" feature shows all changes, in case framework objects for multiple databases are in the same database, when using shared model
• SQL Server Management Studio becomes unresponsive and closes when connecting to a local SVN repository if it is not available
• The "Action center" tab is broken form inside SQL Server Management Studio
• Deleting objects in shared model doesn't work for Perforce and Mercurial
• The "Action center" tab shows wrong message when linking static data
• The add-in doesn't inform the user that a database is already linked using different development model
• The progress bar is working indefinitely when linking a database to a local SVN repository
• The add-in throws an exception instead of a user friendly message when connecting to SVN set for https with http
• "Conversion failed when converting the nvarchar value to data type int" error is encountered when trying to create a table in SQL Server Management Studio 2008
• Shared model will not work properly if two users link different databases, but choose the same database for storing the framework objects
• Framework objects are not removed on unlinking, in case two users link databases from the same server, when using shared model
• User value won't be removed from the corresponding framework table, when the user unlink the database
• Object will be initially linked if applying any filter from the filter row in the "Action center" tab
• Clicking the "Check all" box in the "Action Center" tab for the first time, fails to check all objects
• Incorrect preview of the database where framework objects are hosted when linking the database already linked by someone else
• The installation wizard offers SQL Server Management Studio integration even if that version is uninstalled
• Inability to view any other version of the specific object from a single changeset in the "Project history" form
• Inability to compare one version of the specific object from a single changeset with any other version in the "Project history" form
• Missing progress bar on changeset selection, or object the changeset selection in the "Project history" form
• Missing filter row in the "Project history" form
• Missing "Previous/Next 10,000 lines" option in the "View all history" form
• Changing the structure of the table with already mapped static data may cause the data loss

Fixes:

• "Source control error: No changes added to commit" error is encountered when simultaneously committing changes to the repository from different databases
• The add-in causes SQL Server Management Studio to stop working when linking the database already linked by other user
• The add-in does not integrate in SQL Server Management Studio if non-administrative Windows account is used

Known issues:

• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories

Enhancements:

• The add-in now successfully ensures only users who made changes can commit them
• The Apply label is now 300% faster when using TFS source control system
• Linking static data from the “Manage static data” form is now 3,400% faster
• Linking static data from Object Explorer for a single table is now up to 500% faster, depending on the amount of data
• Opening/refreshing of the “Action center” tab is now 1,400% faster

Fixes:

• There is no way to continue the script execution process if there is an error while loading objects from script for applying to database
• The "Action center" tab does not work properly in SQL Server Management Studio 2008
• Source control system switches to the "Working offline" mode, without asking for credentials
• The user can commit changes to source control made by other user
• "Some framework objects could not be created" error is encountered when a single project is used for different development model
• "Ssms20xxRegistrator.exe" cannot be executed successfully during the installation, causing the add-in fails to integrated within SQL Server Management Studio
• Missing drop down list for the "Action" state in the "Action center" filter row
• Missing icon for the state of the "Action" column in the "Project history" dialog
• Redundant comment column in the "Project history" form
• The "Source control" wizard allows creating the new project in the "Chose project" dialog but project will not be created and thus cannot be selected
• "Source control error: AddFolder failed with message 'Message:MCKCOL request on "path"' failed: 405 Method not allowed" error is encountered when trying to create a new project
• "Could not get the list of items for the folder on the server. Check credentials on the repository path" error is encountered when trying to browse projects in the "Source control" wizard
• After committing the database to source control, wizard will change the repository incorrectly to the last commit folder
• The add in marks the database as linked to source control even when an error prevents the actual commit of any object to source control
• The add-in allows creating label even on an empty repository
• The add-in causes SQL Server Management Studio to become not responsive when canceling the "Apply" operation from the repository to database
• Multiple users have an option to choose the database where the framework objects will be installed
• The add in installs default config files and SSMS2012registrator.exe in wrong administrator account instead of the current user account causing the add-in is not registered with SQL Server Management Studio
• Creating label when using TFS source control system gives an exception
• Static data table names in the "Action center" tab is not correctly specified, when the static data differs from the static data stored in the repository, depending on the name convention used
• Static data changes will not be applied if there are more data rows in the database table than in the table stored in source control
• Schemas won't be shown in the add-in options, when switching from one database to another, and getting back to the initially selected database
• Databases cannot be unlinked from source control when trial period expires
• Single column data will be deleted when applying changes from the source control, if there are more data rows in the database table than in the table stored in source control, and at least one row is different
• Excessive slash in the repository name shown in the SQL Server Management Studio status bar, when the project is nested in the repository
• The add-in shows incomplete information in the SQL Server Management Studio status bar
• "Unexpected error: Operation was canceled by user" error is encountered when pressing the "Cancel" button or the "Close" button in the "Get label" dialog
• The "Comment" section overlaps the object list if there are not enough space
• The add-in cannot recognize the presence of source control system for already linked database and will ask for a password
• The add-in thread cannot be removed from SQL Server Profiler
• "Object reference not set to an instance of an object." error is encountered when switching the "Action center" tab from offline to online mode
• Clicking the "Send logs" button blocks SQL Server Management Studio, and makes it unresponsive until the email is sent
• Changing the source control system from the drop down list in the "Source control" wizard switches the development model to dedicated, when shared model is selected
• When clicking the "Script with dependencies" check box, the operation cannot be canceled
• Excluding objects from monitoring fails to apply to the object explorer icons after the specified time period in the add-in options
• Icon for SQL function is not visible, when object is checked out using the Shared model or edited using the Dedicated model
• When using Perforce source control system, wrong information is shown in the SQL Server Management Studio status bar
• The "Post_Save notification" message box is not informative enough, when changing an object in shared development model, with the "Check out before edit" policy enabled
• The "Action center" tab shows the object after resolving conflict, even if there are no differences between local database and the repository
• Informative message in the "Administrator " tab cannot be set to be shown when it is disabled
• The "Previous" button is excessive in first step of the source control wizard
• "Out Of Memory exception" error is encountered in MergeDiff window when showing large scripts ( > 20mb)

Known issues:

• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories

Enhancements:

• The add-in now supports source controlling of static data
• Export / import object change tracking settings is added
• The "Apply" operation is up to 300% faster on committing objects to a repository when working with Team Foundation Server

Fixes:

• Changing database during the object comparing/loading in the "Action center" tab results in false object state
• "Object reference not set to an instance of an object" error is encountered, when expanding the database node in Object Explorer
• The "Action Center" toolbar button is active even when the highlighted database is not linked to source control
• The "Action center" tab shows SQL Application role object as different because only Roles are supported
• Undoing changes before the first commit drops the object
• Missing an informative message that the database is already linked using one of the development models, when trying to link a database from other machine
• "Object reference not set to an instance of an object" error is encountered on initial commit, when filtering schemas in the source control wizard
• The framework object "ApexSQL_SC_DatabaseLog" will be deleted from the wrong server when unlinking the database
• "Strong-name assemblies must specify a public key in their InternalsVisibleTo declarations." error is encountered when connection to Git source control repository using the SSH connection
• The add-in fails to link a database to source control if the database with the same name is already linked from the same machine
• The add-in fails to recognize specific database schema
• The "Save" button in the add-in options is redundant
• The "Logging info" table contains excessive words in column names, and the column order is not properly set
• When executing the "Get" command of the schema changes without static data from the source control to a database, the progress dialog stays opened indefinitely and the "Get" task will not be accomplished
• The add-in cannot work in environment where SQL Server Management Studio 2008 R2 Enterprise is installed
• The add-in causes SQL Server Management Studio to not responding state, when trying to connect to any source control system without specifying any connection parameters
• Missing warning message that database policies are changed before closing the add-in options
• The add-in fails to run properly if the version of SQL Server and SQL Server Management Studio are not the same
• Missing informative message in the "Action center" tab when there is no differences between local and source control repository
• Missing progress bars and icons in the "View all history" form
• The "Administrator" tab remains enabled even if there are no databases linked using the Shared database development model
• The installer does not recognize SQL Server Management Studio version properly
• The "Action center" toolbar cannot be disabled in SQL Server Management Studio toolbar
• Inappropriate "?" icon for credential object type
• The project created in the add-in wizard cannot be found on Visual Studio online repository
• Add-in table from tempdb will be deleted after SQL Server is restarted from SQL Server Management Studio
• The add-in is not selecting all objects on first database linking
• Missing informative message that the "Action center" tab needs to be refreshed after making changes in the database
• Clicking the "Get" button in the "View version" section closes the window and makes SQL Server Management Studio unresponsive, until the "Sync" is shown

Known issues:

• The “Source control” wizard closes if the repository path is wrong, when trying to connect to Subversion source control system
• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories

Fixes:

• The system objects are not created properly in the user database, after linking it to source control
• The "CREATE TABLE permission denied in database 'tempdb'. Changed database context to 'tempdb'." error is encountered when add-in wrongly attempts creation of the table in the temp database when using the shared model
• The add-in creates wrong trigger when version of the SQL Server Management Studio version is different from the SQL Server version that hosts the database
• The "Object reference not set to an instance of an object" error is encountered during initial committing of SQL objects to the TFS repository which already contain scripts

Known issues:

• The add-in is not working with old shared model after the update process
• The “Source control” wizard closes if the repository path is wrong, when trying to connect to Subversion source control system
• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories

Fixes:

• The "Action center" tab cannot complete the "Comparing objects" process on extremely large databases
• The "Source control" wizard closes on the "Configure monitoring" step when linking large database to source control
• The add-in causes SQL Server Management Studio to stop working when linked database contains the "-" character in title
• Missing informative message that system objects are not created successfully after the database linking process
• "Committing while offline is possible only for distributed SC systems like Git or Mercurial" message appears when trying to commit anything to an empty repository using Perforce
• SQL Server Management Studio hangs each 60 seconds when extremely large database is linked to source control
• If SQL schema is excluded from types, in the add-in options, the script for dropping object will be generated during commit from source control for all schema scoped objects
• "Could not load file or assembly p4api.net.dll" error is encountered when trying to connect to Perforce source control system
• "Unexpected error: There was nothing to sync between Source Control and Database" error is encountered when trying to get an object from source control
• Selecting object in the "Action center" tab is taking too long, for a large database
• Excluding objects from monitoring in the add-in options will be wrongly presented in the "Action center" tab
• The DNS address "tfs.xxxxx.net" cannot be resolved when Team Foundation Server is in a different domain and "Error 404" message will be displayed

Known issues:

• The add-in is not working with old shared model after the update process
• The “Source control” wizard closes if the repository path is wrong, when trying to connect to Subversion source control system
• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories

Enhancements:

• Rewritten shared database development model:
  • Support for Git and Mercurial source control systems
  • Communication with source control repository using the Action center tab
  • Edit objects from SQL Server Management Studio
  • Work offline feature is implemented in Action center tab
• An option to prevent objects from being edited if locked\checked out is added
• An option for development policies is added
• The add-in now supports Perforce source control system
• The "View all history" feature is added for a source control project
• The "Multiselect" feature is added in the Action center tab
• An option to exclude objects from monitoring by type, schema and name is added
• An option for logging changes made to the database schema is added

Fixes:

• The "Apply all from source control" feature will generate an incorrect script for some objects and the subsequent operation will fail
• Label 'tip' is present in "Show labels" feature even if it is not made for databases linked to Mercurial repositories
• "Illegal characters in path" error is thrown when comparing objects
• The Source control wizard will close if a source control system is changed after initial login
• The "Go offline" feature is missing in the Object Explorer for the new shared model
• The add-in causes SQL Server Management Studio to stop working after clicking the "Cancel" button when the "Warn about pending changes on exit" option is enabled
• Missing info message that policy cannot be/is successfully changed
• SQL Server Management Studio stopped working if incorrect Perforce credentials were used during the database linking process
• "Timeout Expired" error is thrown when linking large database to Subversion during object linking process
• The "Action center" tab will not display dependent table after data-type changes are made
• The add-in fails to ignore the default objects created when using TFS Online
• "Object reference not set to an instance of an object" error is thrown when applying message type to source control
• The add-in does not revert changes to a local working folder when commit fails with an exception
• The default location for add-in files is changed after a specific Windows update
• The Perforce workspace is not removed when linking database to a previously created workspace after un-linking the database
• Creating Label on Dedicated database is up to 5 times slower than on Shared database
• The "Compare versions" option does not work in the "View history" window
• The "Copy to clipboard" option does not work in the "Apply changes to database" window
• The “There is no info about the previous state of the object” message will appear when the Undo operation is performed in the Action center tab
• Object state icons for shared model are not changed correctly
• Missing informative message that a policy cannot be/is successfully changed
• After the object is checked out, edited and checked in again, the "Action center" tab will open with the selected object, but it is not in focus and the selected object's label says ": 0"
• Clicking on "0" revision on the "View all history" for Subversion throws an error for shared model
• The "Action center" tab will stay open after disconnected from server
• Activation is required after upgrade from previous version
• The add-in can be installed even when there is no host application installed
• "Path not found" error is encountered when connecting two databases to the same Team Foundation Server project
• Performance issue when refreshing the Action center tab while connected to a Team Foundation Server repository

Known issues:

• The add-in is not working with old shared model after the update process
• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories
• The DNS address "tfs.xxxxx.net" cannot be resolved when Team Foundation Server is in a different domain and "Error 404" message will be displayed

Changes:

• Support for SourceGear Vault source control system has been deprecated

Enhancements:

• Conflict resolution using integrated merge tool
• Added option to script changes with\without dependencies when applying them to the database
• The "Filter" feature is added for database objects in Action Center tab for dedicated database model
• Added option for obligatory comments with enlarged comment field in Action Center tab for dedicated database model
• The "Apply all to source control" operation is up to 200% faster when working with Git
• The "Refresh" operation is up to 700% faster when working with Subversion

Fixes:

• The "MergeDiff" feature will block Action Center tab from opening for the first time add-in installations
• The "Source control wizard" will enable shared development model for Git before database is linked for the first time
• User will be asked for evaluation on every SQL Server Management Studio restart
• The "Source control wizard" will close when SourceGear Vault is selected
• The "Remove link from source control" is not working in SQL Server Management Studio 2005
• The "Get" from source control operation cannot be performed on database witch names start with numbers
• The "Work Offline" message will not be displayed when Action Center tab is detached
• The "MergeDiff" feature will show false script differences when Action Center tab is open and the database is set offline
• The "Restore previous version" operation will fail sometimes
• The "Test" feature in the "Source control wizard" is not checking credentials for Subversion
• Changed database objects are still marked in the Object Explorer after "Get" of previous database label is performed
• The "Check out" operation is not possible every time on shared database linked to Subversion
• Committing over 2000 objects on CloudForge, GitHub or Bonobo servers the "Prepare object for commit" process will get slower over time
• Object changes will not be reverted when "Cancel" is pressed during the "Prepare objects for commit..." step
• Changes in "View history" will be shown only if Object Explorer is refreshed after commit to Git
• The "Compare version" feature will not display last changes in the "Database version" tab
• The "Object source control status check-up interval" option in Options dialogue doesn't have defined time measurement unit
• The "Setup has detected that SQL Server management Studio is running" warning message is displayed even if SQL Server Management Studio is closed
• The progress bar will stay open over "The file xyz already exist. Overwrite it?" dialog after adding a table to source control
• The "Check out" dialog is missing icon for some database objects
• The "Get specific version" feature in the "View history" will throw error during script execution over shared database linked to Team Foundation Server
• The "Update object to the specific / latest version in SC" feature will throw an error over shared database linked to Team Foundation Server
• The "Error 404" message is displayed when the GIT repository is used for Mercurial and vise verse
• The "Remove link from source control" is not working every time on shared databases
• The "Commit failed" dialog is missing additional info why this actually happened
• The "Action Center" buttons from SQL Server Management Studio toolbar will state that the database is shared
• The "Log in" dialog will appear if Action center tab is in offline mode
• The "Source control wizard" cannot finish database linking process if the wrong Subversion login info is used
• The Object Explorer will not mark object states under source control in real time
• The add-in delete tables from a local database when it is applied to source control without related schema
• XML schema collection, Contract and Message type are carrying same objectID and the Object Explorer will mark all changed objects as check in after only one object is

Known issues:

• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories
• Label 'tip' is present in "Show labels" feature even if it's not made for databases linked to Mercurial repositories
• The add-in is not backward compatible with 2014 version or lower

Enhancements:

• The add-in now fully supports dedicated database development model
• The add-in now supports Git, Mercurial and Visual Studio Online
• The add-in now supports HTTP, HTTPS and SSH connections
• The add-in is now completely integrated into SQL Server Management Studio
• The add-in is now supports SVN and SVN+SSH connection protocols
• Real – time monitoring of changes made to database objects
• Comparison algorithm that monitors nature of the changes made between database and source control and offers default actions based on them
• Generating dependency aware, atomic scripts for synchronizing database with source control
• View differences between individual object scripts feature is implemented
• Conflict resolution using third party tools: KDiff3, BeyondCompare and ExamDiff Pro feature is implemented
• Undo changes made to the database feature is implemented in Action center tab for dedicated database model
• Get by version feature is implemented in Object Explorer pane for dedicated database model
• Create label feature is implemented in Object Explorer pane for dedicated database model
• Get by label feature is implemented in Object Explorer pane for dedicated database model
• Work offline feature is implemented in Action center tab for dedicated database model
• Improved Source Control wizard for more intuitive database linking to source controls
• Customized menu based on chosen database model

Fixes:

• Differences window in "Action center" tab will freeze after "Get from history" feature is performed and SQL Server Management Studio needs to be restarted
• The "No pending changes" message will be displayed when attempt to make a new folder in project root is performed on Team Foundation Server
• The "Source Control Wizard" will make database folder in DedicatedData when "Test' button is pressed or connection to source control has failed
• The GitHub will state offline mode in "Action center" tab and commit will fail every time
• The add-in will not integrate in SQL Server Management Studio 2008
• Object differences will not be shown in "Action Center" tab if some operations are performed on other shared database
• Bad data changes in "Action Center" tab are shown in case two or more databases are linked to Mercurial repositories
• The "Cannot get folder" message is displayed when "Get label" feature is performed on a database linked to the project root
• Reports are not working and the "An error occurred during local report processing" message is displayed
• The "Check in" feature is not working on Subversion shared database
• The "Invalid Object name tempdb. Dbo. DatabaseLog" message will be displayed when changes are made on the table
• Tool tips will disappear after sorting in "View history" feature tab
• Individual objects will not be added under Subversion shared database
• The "Remove link from source control" feature will not delete DatabaseTriggerLog trigger
• Commit changes in data type will not empty tempdb. dbo. DatabaseLog
• SQL Server Management Studio stopped working if Subversion login information is provided for user without password on the dedicated database
• Commit to the remote Git repository set up in a local file system is not possible
• Bad data changes in "Action center" tab in case two or more databases are linked to Git repositories
• Connect to a local Git repository using "file:\\" prefix is not possible
• The "Remove link from source control" feature will not delete files from temp folder
• SQL Server Management Studio will freeze after some time without usage when "Action center" tab is open
• The "Undo check out" feature will not revert state before "Check out" and latest change over the object
• The "Get latest" feature is not working under Team Foundation Server shared database
• Actions cannot be performed over databases linked to the root folder as Subversion dedicated database
• The "Get from history" feature is not working correctly under Subversion dedicated database
• The "Get label" feature is not working correctly under Subversion dedicated database
• The "No pending changes" message will be displayed when attempting to make a new folder in root project is performed on Team Foundation Server shared database
• Detaching "Action center" tab will display incorrect "Work offline" feature info
• Label will be created without any information or progress bar
• The "Apply label" function is offering to delete tables added in the meantime for Git and Mercurial
• After "Apply all from source control" feature is performed under Git with only one change, tooltips on an "Action center" tab will disappear
• Apply label under Git and Mercurial will throw "cross thread" exception if there are no differences relative to the database
• The add-in dialogs will be opened out of SQL Server Management Studio focus
• When "Remove link to source control' feature is performed "Action center" tab will stay open and error will be shown
• The "Undo" feature over a large number of selected objects will stuck on "Creating script..." step and "Cancel" cannot be performed
• Click on "?" button will close windows and help will not be initialized
• The localcache.xml file isn’t updating and object changes are lost
• The "Initializing" progress bar is always across dialogs
• The "Get by label" feature will not be fully completed
• The "Object reference not set to an instance of an object" error is thrown when "Cancel" is pressed during the refresh process on large database linked to Subversion

Known issues:

• There is no history for renamed objects in "View history" feature for databases linked to Git or Mercurial repositories
• Label 'tip' is present in "Show labels" feature even if it's not made for databases linked to Mercurial repositories
• The add-in is not backward compatible with 2014 version or lower

Changes:

• Support for Visual Source Safe source control system has been deprecated

Changes:

• The add-in name is changed from ApexSQL Version to ApexSQL Source Control

Enhancements:

• The add-in now fully supports SQL Server 2014
• The add-in now supports Apache Subversion up to version 1.8.9
• The add-in now supports Team Foundation Server 2013
• Linking objects to Apache Subversion is up to 300% faster

Fixes:

• The add-in cannot link all selected objects to source control while leaving a database in a non-linked state
• The "Check out" feature works very slow and brings SQL Server Management Studio occasionally in a non-responding state while the "Progress info" dialog disappears from the screen occasionally
• The "System.OutOfMemoryException" error is encountered in SQL Server Management Studio when linking objects of a large database to source control
• The "Update object" option doesn't work
• The "Check out" status icon in the "Object Explorer" pane is hardly visible, making hard for the user to quickly determine status of the object
• SQL Server Management Studio hangs when multiple medium to large databases are connected to source control
• The SQL foreign keys are lost when a table connected to source control is edited
• Objects connected to source control are marked as "Not in database"
• The "Apply to database after editing" option will have no effect as the add-in will always use the value "Prompt" when editing
• The add-in will wrongly check in an object when the user clicks the "Cancel" button instead of the "Check in" button in the "Check in <object>" dialog and an object will stay in the checked out state
• The add-in will check in an object to source control before editing even when the user explicitly cancels it, when the "Check in to source control before editing" option is set to always
• The "Assertion failed at ApexSQL.Common.SourceControl.UI.Forms.Select.Project.From.btwNewProject_Click" error is encountered when attempting to create a new Apache Subversion project via the "Source control" wizard
• The Red Gate Source Control add-in overrides the add-in's database overlay icon in the Object Explorer pane
• The "Access to "/" forbidden" error is encountered when trying to connect to the CloudForge Apache Subversion server
• Same object cannot be removed and then added back to source control
• The "Evaluation" dialog pops up when the add-in is started, or the "Link database to source control" option is chosen
• The "The process cannot access the file <path>\Options.xml because it is being used by another process." error is encountered when multiple SQL Server Management Studio instances are opened
• SQL Server Management Studio hangs and the "Refreshing" window will stay open after large database is linked on source control

Changes:

• New user interface that follows Metro UI style

Known issues:

• The "System.OutOfMemoryException" error is encountered in SQL Server Management Studio when linking a database to source control with all objects linked for large databases

Enhancements:

• Add-in now supports TFS 2012
• Add-in now supports Vault 6.1

Fixes:

• "Database vs Source Control" and "Database linking status" reports are generated blank
• Source control reports should be created in the "Multiple Document Interface" window in SSMS
• The 'Description' form is not consistent with the 'Extended property edit' form
• In the 'General' tab of the visual object editor, the scale can be set to a higher value than the precision value for numeric and decimal data types
• User data types in sequences do not contain a schema in the 'Data type' droplist
• "Database vs source control difference" instead of "Database linking status report" is shown when using the "Linking status report" option
• The 'Exception: Getting db script for diff report: Index of object [dbo].[t1] is changed' error is encountered when an object under Source Control is recreated
• The SSMS 'Table Edit' window loses its focus and cannot be recalled back even when clicking on the SSMS window
• The missing option to remove multiple objects from Source Control in 'Edit Source Control Setup'
• The Search property list title is misspelled as 'Searchpropertylist' in the confirmation dialog for the 'Remove from Source Control' option
• The add-in is catching and logging errors from non ApexSQL add-ins installed in SSMS
• On 'Edit' or 'Check out' of any Full text stoplist, the Save button becomes enabled as soon as the visual editor dialog is opened even if no changes are made
• There's no progress bar or any progress indication when calling time demanding context menu operations
• The non ApexSQL application appears in the ApexSQL Version's main menu if both add-ins are installed in SSMS
• The not supported 'Label' feature is shown in the ApexSQL Version's context menu for database objects linked to Source Control via Subversion native drivers
• Property values for 'Search property list and Sequences' are not included when importing and/or exporting default linking settings
• No information message appears when an object is added to Source Control
• There's no progress bar when creating database objects type subfolders
• Users and roles on the 'Permissions' tab in the visual editor are listed wrongly
• The "A database name must be specified" message is shown when editing synonyms while the database is linked to Source Control via SVN
• The 'Drop & Create' object script is generated in the 'Visual Editor's Script' tab when editing 'User-Defined Data Types' even if no changes are made
• There's no visual progress indicator in the Source Control configuration when the Test button is clicked in Source Control Wizard
• The "Object reference not set to an instance of an object." error is shown when a table is renamed via the ApexSQL Version's visual editor
• The drop-down list for the schema selection is empty in the 'Properties' pane of the visual table editor
• It is not possible to change a table's schema while editing any table
• The 'There are multiple root elements .' error is shown when editing an XML schema collection via the visual editor under the VisualSVN
• The object removed from Source Control is offered as a valid candidate for the 'Get Latest Version' command when native Visual SourceSafe drivers are used
• The ">file_name_with_full_path< is not a working copy" error is shown if the working folder is empty while the 'Undo Check Out' operation is performed
• During the trial period, even if the 'Evaluation notice' dialog is closed, it is possible to enter the application
• The SourceGear Vault service version 6.x is not supported in Source Control via native drivers
• Using the Object Editor to edit the structure of a SQL stored procedure results with being unable to edit the SQL stored procedure's signature via the 'SQL Body' tab
• Editing a live object whose SQL script is under version control results in the incorrect version of the script being checked out by the add-in

Changes:

• The add-in menu is now under the "ApexSQL" parent menu

Enhancements:

• Navigation through the Object Explorer has been significantly improved in all SQL Server Management Studio versions. The speed gain depends on the number of the objects in the database and starts at 500% when working with a database containing a few hundred objects of the same type
• The generation time of the "Database linking status" report has been significantly lowered particularly on databases mapped to Subversion via native drivers. The speed gain depends on the number of objects in the database and starts at 1700% for databases containing few hundred objects
• Mapping databases to a remote Subversion server via native drivers as well refreshing the Object Explorer for such databases has been greatly improved. The speed gain depends on the number of the object types mapped. For databases containing several hundred objects of different object types, the mapping process can be up to several times faster
• A progress indication dialog is now shown while the "Database vs. Source control differences" report is being generated
• A progress indication dialog is now shown in the "Configure linking" step of the "Source control wizard", while adding a database to source control
• The add-in doesn't affect the time needed to generate a CREATE script for SQL full text stoplists any longer
• Checking out databases and objects linked to Subversion is now up to 300% faster

Fixes:

• Navigating databases and tables in the SQL Server Management Studio's Object Explorer on a remote SQL Server connected via VPN is five times slower if the add-in is installed
• ApexSQL Version commands are not disabled for databases that are not linked to source control
• Changes made to the contract object type in the "Visual editor" cannot be saved when VisualSVN is used
• Services created under the queue object type cannot be versioned via the add-in, as an update script is not generated for modifications performed via the "Visual editor"
• Message types cannot be properly handled via the add-in, as an update script is not generated for modifications performed via the "Visual editor"
• The "Modify remote service binding" command via the add-in fails because the update script is not generated
• Updating routes via the "Visual editor" does not work because the update script is not generated
• There is no warning during the add-in's installation process which informs the user if Visual Studio and/or SQL Server Management Studio is running
• The add-in can be uninstalled while SQL Server Management Studio is active resulting in an incomplete uninstall
• The "ErrorFileAlreadyExists" error is encountered after connecting a database to the Team Foundation Server 2010 using a MSSCCI provider and initiating a source control object status refresh
• Cancelling during the "Confirm linking" step of the "Source control wizard", results in SQL Server Management Studio being non-responsive
• The synchronization script is not updated in the "Generated script" tab after adding a new SQL search property when editing the SQL search property list object
• The "Use version from source control" option in the Select object version dialog, loads the database version when editing a table which differs between the source control and the database
• The "Use version from source control" option in the Select Object Version dialog, loads the database version when editing a procedure which differs between the source control and the database, and was previously edited and checked into the database that was linked to Subversion via the Native driver
• The changes are automatically applied to a database after object editing, when the "Apply to database after editing" option is set to "Never"
• The Object Explorer context menu commands "Database vs. Source control differences" and "Show database/Source control script differences" don't open the corresponding reports in SQL Server Management Studio 2005 without Service pack 1
• The Help request invoked by F1 or the "?" button while an object edit dialog is active, opens a non-existing web page
• The text of the two options in the Select the object version dialog is not fully visible when using the 120 DPI system font resolution
• The text of the Edit queue dialog options, "Maximum queue readers" and "Poison message handling", is overlapped by their corresponding value entry controls when using the 120 DPI system font resolution
• The Check-out comment dialog text overlaps the comment edit box, and the "Don't show this again" checkbox text is not fully visible when using the 120 DPI system font resolution
• SQL Server Management Studio displays a depreciated "ApexSQL Version Edit" toolbar with all commands disabled
• High memory leakage and CPU load lead to SQL Server Management Studio 2012 unresponsiveness when expanding a database node, in scenarios where 3 or more large databases are linked to Subversion via native drivers
• The error message "Nije uradjen check-out", when updating an object that was not checked out, is not in English
• Immediately after linking a database to a source control, the differences report shows that all database objects are different from their source control versions
• Objects cannot be linked to a source control via Team Foundation Server native drivers if each object type is not linked to its appropriate subfolder
• The "access to the path >working folder location< is denied" error is shown on attempting to check-out any object, if the database is linked to a Team Foundation Server via MSSCCI drivers
• The "access to the path >working folder location< is denied" or the "Error AccessFailure" error is shown on attempting to check-out any object, if the database is linked to a SourceGear Vault via MSSCCI drivers
• SQL full text stoplists created via system stoplists cannot be processed by ApexSQL Version, as changes applied via the "Visual editor" are not handled
• The "Object reference not set to an instance of an object" error is encountered when attempting to processing SQL FileTables using "Visual editor"
• Database objects removed from source control are marked as different in the "Database vs. Source control differences" report
• Displaying the context menu for any database object linked to source control does not retrieve the correct information on whether the object has been linked to source control
• A checked out without saving, and then changed and saved SQL table is always reported as the same as the version in the source control
• When adding ole members while editing a SQL role, the "Select a database role or user" dialog doesn't have a system menu icon in the top left corner and can be resized to hide all of the UI elements
• Increasing the number of objects significantly increases the time needed for the "Confirm linking" operation
• The add.in doesn't follow the proper version number form in "Add/Remove Programs"

Changes:

• The Source control wizard requires "/vaultservice" to be appended to the SourceGear Vault server address when connecting to the SourceGear Vault server via the native drivers
• The "Object source control status check-up interval" option has been disabled by default in order to improve SQL Server Management Studio's responsiveness
• The "View history" command has been removed on the database level

Enhancements:

• The add-in now fully supports the following SQL Server 2012 object types:
  • FileTable
  • Sequence
  • Search property list
• Visual editors have been introduced for editing versioned objects allowing the following to be edited:
  • DDL
  • Properties
  • Extended properties
  • Permissions
• Improved security: Certificates cannot be versioned any more

Fixes:

• Context menu commands not applicable for the selected object are always enabled if the add-in is installed under SQL Server Management Studio 2005 pre-Service Pack 1
• A database linked to a SourceGear Vault server 5.1 repository via Native driver is no longer displayed as linked after restarting SQL Server Management Studio 2005 pre-Service Pack 1

Enhancements:

• Add-in now works in SQL Server Management Studio 2012
• Add-in now supports SQL Server 2012

Fixes:

• Add-in is not available in SQL Server Management Studio 2012 after applying KB2645410 system update
• "Object <object name> not found in the database" error is encountered when using Update Object | To Specific Version in Source Control command for User Defined Data Type
• Update Source Control command checks in empty object script to source control repository if the object was previously modified
• "Method not found" error is encountered when using Update Object | To Specific Version in Source Control command if ApexSQL Refactor 2011.01 add-in is also installed
• "The type initializer for 'ApexSql.Common.Activation.DllActivationManager 1' threw an exception" error is encountered when attempting to Check for Updates if ApexSQL Complete 2012.01 add-in is also installed
• "Object reference not set to an instance of an object" error is encountered after linking a database to source control if the database was taken offline
• Database and source control versions of recently linked and unchanged Table will be reported as different when checking out the Table
• Add-in log file contains log entries from other installed ApexSQL SQL Server Management Studio add-ins
• New objects are checked in to source control with 'ApexSQL Edit Automatic Operation' comment by Update Source Control command
• Source Control Wizard opens ApexSQL Complete help when this add-in is also installed
• "Value does not fall within the expected range" error is encountered when using Add Object to Source Control command after changing source control linked database's working directory
• Background source control to object explorer object status refreshing stops working over time
• Modified object script is still checked in to source control after difference viewer is cancelled
• "[Online] info operation error for..." error is encountered during check in if the password used for connecting to Subversion repository via Native driver has been changed after logon
• Incorrect logo image is displayed in add-in generated reports
• "Could not connect to..." error is encountered after source control login dialog shown for Add Object to Source Control, View, Edit, Update Source Control or Remove Object from Source Control commands is cancelled
• View Labels command for database linked to Subversion repository using Native driver warns twice about unsupported labels
• Source Control Wizard dialog size and position aren't preserved between sessions
• Source control operation warning message dialogs have ApexSQL Refactor or ApexSQL Complete title when those add-ins are also installed
• "The database was successfully linked to Source Control" message box doesn't have add-in name in the title
• Support Forum main menu command opens ApexSQL Refactor support forum page

Changes:

• Source Control Wizard | Configure Linking Export and Import file save/load dialogs default location is now "ApexSQL\Version" path under user documents folder
• Object Edit command now displays database and source control version selection dialog before the check out dialog if the database and source control object scripts are different

Known limitations:

• Background source control to object explorer refreshing stops working over time
• "ApexSql.SourceControl.Exceptions.OperationException" error is encountered if the password for connecting to Subversion server is changed on the server itself