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.
Conflicts between SSMS native Intellisense and the ApexSQL Complete hint-list
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:
The ALM files are bulking up and using too much space
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
“Check-in failed Source control error: Cannot checkin pending changes” error
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.
“Connection was failed with message: ‘The executable did not complete within the allotted time’” message
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.
“Could not allocate space for object ‘<object_name>’ in database ‘<database_name>’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.”
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
User defined snippets, auto-replacements, aliases, executed queries, tab navigation are not available after the upgrade
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.
Incorrect warning message ‘Only customers with a current support and upgrades contract can upgrade for free…’ is displayed in the application update dialog when new application version is available for free tools and tools with ‘Community edition’
Applies to
ApexSQL Diff, ApexSQL Data Diff, ApexSQL Doc, ApexSQL Script, ApexSQL Complete, ApexSQL Search, ApexSQL Refactor
Summary
This article explains what to do when ‘Only customers with a current support and upgrades contract can upgrade for free…’ warning is encountered when application update is initiated for free or Community edition ApexSQL tools.
How to manually install and uninstall ApexSQL Log 2014 server side-components
Applies to
ApexSQL Log 2014
Summary
This article explains how to manually install and uninstall the server side components when it is not possible to utilize ApexSQL Log installer or when server side components need to be (un)installed on the passive cluster node.
The ‘Sqlcmd: Error: Syntax error at line XYZ near command ‘X’ in file ‘file_name.sql’.’ error is encountered when running SQL script via sqlcmd utility
Applies to
ApexSQL Recover, ApexSQL Log
Summary
This article explains how to manually edit script created by ApexSQL Recover or ApexSQL Log which contains ‘$’ sign in order for it to be executable by sqlcmd
