Prior to downloading this Software, you must review the Software Transaction Agreement located here and confirm, by clicking the I agree check box below, that your organization accepts and is bound by the terms and conditions of the Software Transaction Agreement for this Software.
If you purchased the licenses for this Software by executing an order form with Quest or if you have an agreement with Quest that states that all purchases are governed by such agreement, then the terms and conditions of that agreement supersedes and takes precedence over the Software Transaction Agreement.
Release: 2021.02.2124 Date: July 13, 2021 Fixes: - 210739: Only objects from the first linked Azure SQL Database in the shared development model can be checked out and locked.
Release: 2021.02.2119 Date: May 12, 2021 Enhancements: - SQL graph tables support - Temporal tables support - Delete button is added in the Labels window - Refresh button is added in the Labels window For more information on this release, please read the release notes.
Add the checkbox to ignore permissions for new objects, or add the intelligence to the existing options so that when it is comparing to “nothing”, it will still ignore the permissions
After clicked on Link static data on the selected table, nothing happened. The icon didn't change and it never showed up in the Action center tab. The different collation between ApexSQL and linked databases is what caused the issue: The database collation for ApexSQL is Latin1_General_CI_AS_KS_WS and the linked database collation is SQL_Latin1_General_CP850_BIN2.
When trying to link a database to the Git repository hosted on Azure DevOps, the Action center tab is opened and it shows that the database is linked successfully.Although the Action center tab shows that the database is linked successfully, there are two problems:1. None of the database objects are committed to the repository. 2. The Git repository on which the database is linked is empty.
When trying to link a database to Git, the Action center of ApexSQL Source Control is shown the name of the whole different database.Also, when the linking on the Git repository is finished the target folder is empty.
Performance of opening new query windows or modifying the stored procedure/function. It takes about 30-50 sec for the first window to open. After the first throttle all new windows for the same database opens fast.In case of opening a new window for another database the situation is same, first time it takes 30-50 secs, then 1-2 sec. Sometimes it takes even more than 1 min.The situation is the sam...
Merge branches dialog is populated with the commits from the current branch regardless of the selected sourceExpected result: Change sets should be retrieved from the chosen Source branch (for example development branch), not from the branch database is linked to (for example test branch)