SQL Solution center round-up – October 18th, 2013 – SQL Server compliance with FERPA and Basel II, database recovery, and methods for auditing failed logins

In the latest SQL Solution center articles, we wrote about SQL Server compliance regulations FERPA and Basel II, SQL Server database recovery from a corrupted file, and various methods for auditing failed SQL Server logins

Here is the short summary for the solutions we covered in the last two weeks:

SQL Server auditing and compliance for FERPA – the article explains what FERPA is, what it ensures, who has to comply with it and how the regulations address SQL Server databases. See what events you should track, how to protect the education records, and how ApexSQL Audit can help

How to audit SQL Server to comply with Basel II – the last in the compliance rules series, the article explains Basel II requests, who has to comply with it and how it affects SQL Server databases. See how to use ApexSQL Audit to provide controlled systems, timely and accurate reporting, and secured information

How to recover from a SQL Server database data-file corruption disaster – the article explains how to recover a database when backups are corrupted. See how to use ApexSQL Log to recover all data to the point of failure, including the portion of data between the last backup and the time of the disaster

The first part of the audit failed logins series – describes the most common malicious scenarios for failed logins – brute-force attacks, SQL injections, and ad hoc distributed queries

The native methods available for analyzing failed logins – SQL Server Management Studio login auditing, the xp_readerrorlog procedure, and the Windows event viewer are described in Part II

Audit failed SQL Server logins – Part III describes how ApexSQL Audit can be used to investigate failed SQL Server logins and its advantages over native tools

October 24, 2013