ApexSQL GDPR Compliance Relief Program

The ApexSQL GDPR Compliance Relief Program is designed to help organizations that use SQL Server for processing and holding personal identifiable information (PII) reduce the cost of complying with GDPR.

GDPR took full legal effect on May 25, 2018 and is intended to protect personal identifiable information (PII) of EU citizens. It applies to all organizations, in or outside the EU, that handle, process, collect and store personal identifiable information of data subjects residing in the European Union.

January 29, 2018

ApexSQL Log 2018 – Product update alert

ApexSQL Log 2018 has been released

About ApexSQL Log: ApexSQL Log is an auditing and recovery tool for SQL Server databases that reads database transaction logs and audits, reverts, or replays data and object changes affecting the database. It restores updated or missing data and objects, and captures information on the user, application and host used to make each change.

November 28, 2017

ApexSQL Log 2017 – Product update alert

ApexSQL Log 2017 has been released

About ApexSQL Log: ApexSQL Log is an auditing and recovery tool for SQL Server databases that reads database transaction logs and audits, reverts, or replays data and object changes affecting the database. It restores updated or missing data and objects, and captures information on the user, application and host used to make each change.

May 24, 2017

ApexSQL Log 2016 – Screen shot tour

Three main menu tabs in ApexSQL Log.

Home tab contains various ApexSQL Log features separated into several organizational groups: sessions, actions, Results and Tools which include majority of ApexSQL Log features:

April 5, 2017

ApexSQL Log vs. SQL Server Change Data Capture (CDC)

Common SQL Server database auditing goals include the ability to

  • achieve compliance regulatory standards,
  • perform data flow checkups, complete internal/external investigations of who changed what,
  • perform post-disaster analysis when data is unintentionally changed and to discover why did it occur, when, etc.
  • maintain history of data changes (before-after auditing)
December 12, 2016