Applies to
ApexSQL Log 2014
Summary
This article explains what should be done when performance problems are encountered in ApexSQL Log
What should I do if ApexSQL Log returns fewer transactions than I expected?
Applies to
ApexSQL Log, ApexSQL Log API
Summary
This article explains what to do when fewer transactions than expected are returned by ApexSQL Log
Windows stops responding after ApexSQL Audit is installed
Summary
The article explains what to do when the operating system freezes after ApexSQL Audit has been installed.
ApexSQL Audit – An error occurred during local report processing
Summary
This article explains how to resolve the issue when ApexSQL Audit’s Web console shows the following error:
- An error occurred during local report processing
- The definition of the report ” is invalid
- The value of the Width property for the tablix ‘ContentTablix’ is “X,X in”, which is not a valid size. Valid sizes may not exceed 455 inches
- The definition of the report ” is invalid
Top ApexSQL Log issues and resolutions – an index to often used TS articles
Performance problems in ApexSQL Log – the main grid is unresponsive
Some ApexSQL Audit Web Reports requirements are not detected
Summary
The ApexSQL Audit installation cannot be completed successfully due to missing prerequisites.
ApexSQL Recover displays the “Database log.ldf cannot be found” error when SQL Server is running on Windows 8.1 or Windows Server 2012 R2
Applies to
ApexSQL Recover 2011.02.1058 and earlier
Summary
This article describes how to resolve the “Database log.ldf cannot be found” problem in ApexSQL Recover when running on Windows 8.1 or Windows Server 2012 R2
ApexSQL Log and ApexSQL Log API show no transactions on Windows 8.1 or Windows Server 2012 R2
Applies to
ApexSQL Log 2011.03.1088 and earlier
ApexSQL Log API 2011.03.1062 and earlier
Summary
This article describes how to resolve the problem when ApexSQL Log and ApexSQL Log API show no transactions when running on Windows 8.1 or Windows Server 2012 R2
Loading a project file saved by ApexSQL Diff 2012 or previous version in ApexSQL Diff 2013 resets and blocks the Object filter and Schema mapping features
Summary
This article explains what to do when you load the Project file created with ApexSQL Diff 2012 or previous versions in ApexSQL Diff 2013 and end up with reset and blocked Object filter and Schema mapping features
“Objects <object_type>.<schema>.<object_name> are not compared yet”
Summary
This article explains what to do if you encounter the"Objects <object_type>.<schema>.<object_name> are not compared yet" error message
