This article explains how to use the Recover table data from a database backup option in ApexSQL Recover that allows you to recover multiple tables stored in a SQL database backup, without restoring the backup itself
ApexSQL Audit provides a range of built-in queries as part of the reporting module that cover the most common user reporting requirements. For more specific reporting requirements, we have provided a possibility to create custom SQL Server auditing reports by using a drag-and-drop technique. If this still doesn’t provide the specific information you need, you will still be able create queries and reports of your own using T-SQL , due to the fact that ApexSQL Audit stores all audited data in a SQL Server database.
ApexSQL Audit stores all configuration and audited data, from local and remote SQL Server instances in a centralized repository database named ApexSQLCrd. The packages with captured data are transferred automatically and safely via network, parsed, and data is stored into the central repository database. This approach makes it is easier to backup and protect captured data.
This article describes the limitations you should consider when working with ApexSQL Audit.
Description The maximum number of audited distributed instances There is no specific limit on the number of auditing instances (remote SQL Servers) that may be audited. The maximum number depends on your environment, the number of transactions executed against audited servers/databases and network bandwidth. The more distributed instances, the more likely it may be for you to encounter performance problems, as a large number of packages transferred through your network can cause bottlenecks.
ApexSQL Restore can attach native or natively compressed backups and backup sets created in SQL Server 2000 and above to any edition of SQL Server 2005 and above, including full and differential database backups as well as transaction log backups
As such, ApexSQL Restore is very useful, among others, in the following scenarios: