The new release of ApexSQL Log, an auditing and recovery tool for SQL Server databases is announced for Q3 2013. As we are closing to the release, we would like to inform you about improvements and changes we have implemented
September 4, 2013ApexSQL Audit for technology center managers
ApexSQL Audit is SQL Server auditing tool, built to make compliance with auditing regulations easy. It provides a wide range of possibilities for auditing access, changes, and security on SQL Server instances, databases, and objects. It also audits executed queries and warnings encountered on tables, stored procedures, functions, and views. Captured information is saved in a centralized auditing repository, and used to create comprehensive reports
August 20, 2013Auditing features comparison: ApexSQL Trigger vs. ApexSQL Audit auditing
As we did in a previous article, we’ll compare auditing features of ApexSQL Trigger and ApexSQL Audit auditing tools. ApexSQL Trigger is an auditing tool for SQL Server databases which audits and reports data changes that have affected a database. On the other hand, ApexSQL Audit is a tool for auditing SQL Server instances including data and objects access and changes, failed logins and security changes.
August 12, 2013ApexSQL Audit fault tolerant auditing – part II
In the previous article we have described how ApexSQL Audit resolves several scenarios to maintain auditing continuity as the SQL Server auditing solution must be reliable as a solution you can trust. Here are the other situations which can lead to auditing breakdowns
August 12, 2013ApexSQL Audit fault tolerant auditing – part I
What is fault tolerant auditing and why it is important
One of the characteristics a SQL Server auditing solution must have is to be reliable. It means that it is a solution you can trust, that doesn’t provide a false sense of security while in fact it is not auditing the parameters set, has information leak, data loss, or in some situations it’s not running at all
ApexSQL Audit is designed to be fault tolerant and handle the situations which can bring to auditing breakdowns
August 12, 2013Troubleshooting and Knowledgebase articles round-up – July 12th, 2013
Here is a summary of our latest KB and TS articles
July 15, 2013SQL Solution center round-up – July 5th, 2013
In the latest SQL Solution center articles we focused on SQL Server database auditing techniques and recovery options
Here is the aggregated summary for the past two weeks:
July 12, 2013Auditing Features Comparison: ApexSQL Log vs. ApexSQL Audit
ApexSQL Log is an auditing and recovery tool for SQL Server databases which audits, reverts or replays data and object changes that have affected a database. ApexSQL Audit is a tool for auditing SQL Server, but without the ability to revert or replay changes. Let us focus on their auditing features and compare them
July 4, 2013ApexSQL Audit 2013 Beta – Product update alert
ApexSQL Audit 2013 Beta has been released
Type: Beta release
About ApexSQL Audit: ApexSQL Audit is a SQL Server auditing tool with a wide range of possibilities for auditing access, changes, and security on SQL Server instances, databases, and objects. It audits queries, execute and security (authentication changes, permissions changes, attempted logins) operations on tables, stored procedures, functions and views, saves captured information in a centralized auditing repository, and provides comprehensive reports
June 24, 2013ApexSQL Audit SQL auditing paradigm
Having an SQL auditing system in place seems like a straightforward way to harden the security of your SQL data. This way you can at least track the activities and changes done to your SQL Server instance and databases, and depending on the specific auditing system you are using, you might even prevent or roll back malicious or inadvertent changes. However, it’s important to keep in mind that just having a SQL auditing system up and running is not enough. Poorly planned or supervised auditing solutions may lull you into a false sense of security, and actually result in you discovering an information leak or data loss much later than if you had no auditing set up in the first place
June 7, 2013
