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.
Whenever an accidental or malicious data loss occurs, it is important to take the most efficient approach in order to perform the most appropriate recovery process and recover full range of lost data. Also, it is important to choose the right tool which will provide the highest possible chance for the successful recovery. This article will provide details on how to ensure that recovery chance is m...
A question that is frequently asked when pursuing the best practice for MS SQL Server database backups is how to ensure no data is lost in cases of a production database disaster
In this article, it will be explained how to use the Send logs feature for sending application log files through ApexSQL tools to the support team.DescriptionEvery ApexSQL tool collects all important information regarding work processes and stores them in the log files. They are a very important part of finding and resolving any issue reported by users.
While a plethora of information on changes made to a database is recorded in transaction log files, SQL Server transaction log reading has always been a big challenge for all SQL Server users since Microsoft never offered a built-in solution which would allow users to immerse themselves and explore the depths of transaction log files. Furthermore, lack of in-house features that would help understa...
What happens when disaster occurs and we only have full database backup that are taken daily?Are those enough for successful disaster recovery of all lost data?
"ERROR : CreateFile() failed (4) for "C:\Backup\******.bak: The system cannot find the path specified" error encountered in the application log files when filtering log results
While using ApexSQL Log to try to recover operations from a backup file that was created with any level of encryption, the application times out and show no results in any way the application offer (Grid, database, file) Log file shows operations like: WARN : Skipped operations at 844D0705:E29AD42D:91B6 since they don't belong to D0735EEF:00000004:9398
ApexSQL Log is unable to remotely connect to Microsoft SQL Server 2008/2008 R2 (x86/x64/IA64) editions. When trying to remotely connect via SQL log tool to any of the aforementioned SQL Server editions, the following error is encountered: Connection to the database on the server failed. Possible reasons are:Connection parameters for the specified SQL Server are invalid SQL Server is not runnin...
ApexSQL Log is a DBA tool and is licensed per SQL Server instance.This means that each instance requires a license. If there are 3 instances, 3 licenses are needed. It's irrelevant whether these 3 instances are on a single physical machine or on three machines. The number of licenses also doesn't depend on virtualization or the number of users.
In these cases the following errors can be found in ApexSQL Log log files:2022-07-13 11:03:03.990 5980 10832 INFO : Opening 'E:\****_***.ldf' log source. Its size is: 75,254,333,4402022-07-13 11:03:11.474 5980 10832 INFO : Found 33,259 raw transaction log operations from 2020-03-23 18:02:38.090 to 2022-07-07 10:00:12.5002022-07-13 11:03:11.474 5980 10832 WARN : Gap in log source d...