SQL Solution center round-up – January 31st, 2014 – HIPAA compliance, SQL formatting, SQL Server memory performance, single table recovery, and SELECT statements auditing

In the last two weeks, SQL Solution center articles continued the series about compliance recommendations for SQL Server DBAs, T-SQL code formatting, and SQL Server memory performance metrics. We also wrote about solutions for auditing SELECT statement execution, and how to recover a table from a SQL Server database backup

HIPAA Compliance for SQL Server DBAs provides general recommendations to comply with Health Insurance Portability and Accountability Act (HIPAA). It shows how to keep the environment secure and controlled, which users should be monitored, how to set security parameters, and more. It also shows how ApexSQL Audit can help SQL Server DBAs meet HIPAA regulations

A new article about T-SQL code formatting – Rules of SQL formatting – Terminating SQL statements with semicolons – focuses on a semicolon. It explains how to use it to terminate SQL statements, what are differences between the GO command and a semicolon, gives code examples and presents semicolon formatting options available in ApexSQL Refactor

The SQL Server memory performance metrics series continues with two more parts. Part 4 – Buffer Cache Hit Ratio and Page Life Expectancy focuses on Buffer Manager counters Buffer Cache Hit Ratio and Page Life Expectancy. Part 5 – understanding Lazy Writes, Free List Stalls/sec, and Memory Grants Pending presents three more memory counters. The articles explain what the counters present, what are expected values and thresholds, how the counter values can be obtained using system views

How to recover a single table from a SQL Server database backup describes one of the top features DBAs would like to have in the SQL Server recovery functionality. The article shows how to recover a table using the INSERT statement combined with a SELECT statement, the SELECT INTO statement, and the MERGE statement, and a faster solution – using ApexSQL Recover

Auditing SELECT statements on SQL Server describes when auditing SELECT statements executed on a SQL Server database is needed, and presents the solutions for tracking who-saw-what. Besides specially developed stored procedures and functions, custom solutions that utilize traces, the article shows how to use SQL Server Profiler, the SQL Server Audit feature, and ApexSQL Audit

January 31, 2014