#APEX SQL RECOVERY FULL#
#APEX SQL RECOVERY WINDOWS#

Simple solution вЂ“ only the main application needs to be installed on the machine which hosts SQL Server, no additional components are required at any point ldf files are included in the auditing job, they should be copied over when possible and read locally to ensure the best possible performance of both auditing and recovery jobs If any transaction log backups or detached. Local auditing is recommended in cases when working on the server machine is available, or in cases when there are one or more SQL Server instances present on the same machine.Д«est performance вЂ“ online transaction log file is accessed locally, hence there is no network performance limitations or traffic dependencies. It offers better performance since the network traffic will not be a decisive performance factor, and allows users to perform ApexSQL Log jobs from a centralized position. In general, local auditing is recommended whenever it is possible or suitable.

In order to decide on the вЂњbetterвЂќ solution for their particular case/environments, users need to understand all pros/cons of local and remote auditing.

#APEX SQL RECOVERY WINDOWS#

In remote auditing, server side components (a simple windows service which allows remote auditing) needs to be installed on the machine which hosts SQL Server which will be audited, yet nothing is installed on the SQL Server itself вЂ“ detailed information on server side components can be found here.Дeciding on using ApexSQL Log locally or remotely greatly differs between users and is based on their environments and company policies, and thatвЂ™s why there is no universal option. In case of remote auditing, ApexSQL Log is installed on another workstation and SQL Server instances are accessed remotely. In case of local auditing, ApexSQL Log is installed directly on the machine which hosts SQL Server, hence SQL Server instances are accessed locally.

With this, ApexSQL Log can be used to undo (or redo) any changes which have occurred on the database and revert affected data to its original state, as if the changes have never occurred. In addition to its auditing capabilities, ApexSQL Log allows users to roll-back or roll-forward any changes which have been audited in SQL Server database transaction log files or backups, including online transaction log, detached transaction logs or transaction log backups.

#APEX SQL RECOVERY FULL#

Users can audit database changes and present in a comprehensive grid, where they can be analyzed and inspected in great detail, including who made the change and when, as well as the before-after change values and full history of affected rows regardless of the auditing method (local or remote). ApexSQL Log can be used both locally or remotely in order to perform auditing and recovery jobs. ApexSQL Log is a SQL Server database transaction log reader which allows users insight into SQL Server database transaction log files and backup.

Apex sql recovery