Applies to
ApexSQL Audit
Symptoms
When adding the remote SQL Server instance in the server auditing list and process failes due to the required server-side components are not installed on the target machine (Windows service which allows auditing of SQL Server instances remotely via the ApexSQL Audit main application), and ultimately leading to the error:
Applies to
ApexSQL tools
Symptoms
This article explains how to setup Microsoft .NET framework 4.7.1 in order to have ApexSQL tools running on a machine without any problems
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 Complete
Symptoms
This article explains what to do when the ApexSQL Complete hint-list requires too much time to load or occasionally “freezes” SQL Server Management Studio.
Applies to
ApexSQL Complete
Symptoms
Sometimes conflicts occur between the ApexSQL Complete hint-list and SSMS’s native Intellisense. In such cases, SSMS’s native Intellisense may overlap the ApexSQL Complete hint-list as shown below:
Applies to
ApexSQL Log
Summary
This article explains what to do when ApexSQL Log temporary files (.ALM type files) take too much space or when the number of .ALM files is too great
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 Audit, ApexSQL Monitor
Symptoms
The error message is telling you that the ‘PRIMARY’ filegroup is full. This article explains how to resolve this error is encountered when working with application. The error will prevent storing any audited or monitored data into a central repository database
Applies to
ApexSQL Complete
Symptoms
After the add-in is updated to the 2016.01.0072 version, auto-replacements, custom created snippets, aliases, executed queries, tab navigation are not imported properly from previous version.
