ApexSQL add-ins
After installing Spotlight Extensions – Tuning Pack into SQL Server Management Studio 18 (SSMS 18) on a system that already has any ApexSQL add-in installed, the Tuning Pack menu will not be shown in SSMS 18 main menu.
The same problem occurs if Spotlight Tuning Pack was installed before any ApexSQL add-ins.
ApexSQL add-ins
With the release of Visual Studio 2019 version 16.2, ApexSQL add-in tabs do not show options in these tabs, aka ApexSQL tabs are empty. This article explains how to find a solution (workaround) when this problem happens.
Applies to
ApexSQL add-ins
Symptoms
With the release of Visual Studio 2019 v16.1, by default, Visual Studio 2019 blocks any synchronously autoloaded package from any extension and shows a notification to alert the user about it on the startup of application:
ApexSQL add-ins
SSMS 18 is no longer in preview mode and is the first General Availability (GA) version of SSMS 18 is out aka
Applies to
ApexSQL add-ins
Symptoms
With the release of Visual Studio 2019, Microsoft added tags in the Extensions and Updates dialog to help quickly understand whether an extension is in Preview, is a Paid extension, or is in a Trial period. This article explains how to find the installation of ApexSQL add-ins in the latest version of Visual Studio when ApexSQL item is not available among the main menu in the host application.
Applies to
ApexSQL add-ins
Symptoms
This article explains how to resolve an uninstall problem when SQL Server Management Studio and Visual Studio are closed and the uninstall info message still appears, informing that SQL Server Management Studio or Visual Studio is running on a machine
Applies to
ApexSQL Data Diff
Symptoms
“Check-in failed Source control error: Cannot checkin pending changes” error can be encountered during the synchronization to the Team Foundation Server repository, when the synchronization script exceeds 300 MB in size This error can be also encountered if the connection speed between local machine and Team Foundation Server hosting service is slow.
Applies to
ApexSQL Data Diff
Symptoms
“Connection was failed with message: ‘The executable did not complete within the allotted time’” message can be encountered during the recomparison after synchronizing to the Mercurial source control repository, when the synchronization script exceeds 300 MB in size. This message can be also encountered if the connection speed between local machine and Mercurial hosting service is slow.
Applies to
ApexSQL Data Diff
Symptoms
The “Cannot insert the value NULL into column ‘ColumnName’, table ‘TableName; column does not allow nulls. INSERT fails.” error is encountered when running ApexSQL Data Diff synchronization script.
Applies to:
ApexSQL Data Diff
Symptoms:
If very large databases are compared, in some cases, the memory limitation of the application may be exceeded. If so this will produce an Out Of Memory error.
© Quest Software Inc. ALL RIGHTS RESERVED. | GDPR | Terms of Use | Privacy
