SQL Solution center round-up – February 15th, 2014 – SQL formatting, recovery of deleted images, SQL Server auditing, security, and compliance

In the latest SQL Solution center articles, we continued with T-SQL formatting rules series, showed how to recover a deleted image or BLOB file from a SQL Server database, and presented new scenarios for SQL Server security auditing and compliance

The Rules of SQL formatting series continues with three more parts. Commas and spacing in T-SQL describes how to format commas when used as separators. Examples for placing commas at the end or at the beginning of a line, as well as for achieving better T-SQL readability by using various spacing options in ApexSQL Refactor are given

SQL code commenting gives tips for T-SQL code commenting and improving code readability and productivity. We showed how to use line and block comments, and how to comment stored procedures, control statements, and clauses

SQL naming conventions and capitalization rules presents the most common naming convention rules and shows how to use ApexSQL Refactor to achieve capitalization consistency among team members

One more recovery scenario is presented in How to recover a deleted image from SQL Server into a file. The article explains how images are stored in SQL Server databases and gives a step-by-step guide to recover a deleted image or BLOB from a SQL database by using ApexSQL Recover

SQL Server database security and compliance explains what SQL Server principals are and why their monitoring important. We also showed how to monitor database user changes via native SQL Server features, such as SQL Server Audit, and by using ApexSQL Audit

We posted two more articles about SQL Server security. Security and compliance in SQL Server lists common security and compliance requirements, gives general recommendations for achieving security and compliance in SQL Server, and shows how ApexSQL Audit helps with being compliant and discovering security risks

Auditing security changes in SQL Server presents solutions for tracking security and login changes. The native solutions are DDL triggers and the SQL Server Audit feature. Another presented solution that mitigates the downsides of native solutions is ApexSQL Audit

Related posts:

  1. SQL Solution center round-up – January 31st, 2014 – HIPAA compliance, SQL formatting, SQL Server memory performance, single table recovery, and SELECT statements auditing
  2. SQL Solution center round-up – October 4th, 2013 – SQL Server compliance with Sarbanes-Oxley (SOX), PCI, and GLBA
  3. SQL Solution center round-up – December 15th, 2013 – compliance guidelines for SQL DBAs, SQL Server performance monitoring, rules of SQL formatting
  4. SQL Solution center round-up – February 28th, 2014 – SQL refactoring techniques and SQL Server auditing
  5. SQL Solution center round-up – October 18th, 2013 – SQL Server compliance with FERPA and Basel II, database recovery, and methods for auditing failed logins
February 15, 2014