How many times have you had a programmer come to you and say they want you (the DBA) to restore their database to sometime prior to when they accidentally corrupted it? If you are doing FULL transaction logging you can do a point in time recovery to restore the database to just prior to when the corruption occurred. But in order to do that you need to know exactly when the programmer corrupted the data, which in a lot of cases is not known down to the second.

Using Dynamic SQL in Stored Procedures

by Additional Articles

SQLTeam.com

Dynamic SQL

Dynamic SQL allows stored procedures to “write” or dynamically generate their SQL statements. The most common use case for dynamic SQL is stored procedures with optional parameters in the WHERE clause.

Future Proofing an IT Career

by Steve Jones

SQLServerCentral.com

Editorial

Steve discusses the ways that you can ensure your IT career continues to move forward.

How much database normalization is enough?

by Ben Kubicek

SQLServerCentral.com

Editorial

Normalization is important for relational databases, but sometimes too much of a good thing can be bad.

Upgrade From SQL 2012 to SQL 2016 - Problem with Certificates

by Mike Good

SQLServerCentral.com

Certificates

You may need to drop and recreate your certificates after migrating from SQL 2012 to SQL 2016+

How to be Accountable for Handling Personal Data

by Additional Articles

SimpleTalk

GDPR

The GDPR is in full effect but meeting the requirements may still be confusing for many companies. In this article, William Brewer discusses what is needed to ensure compliance, including when a Data Protection Impact Assessment is required. He also explains the Data Protection Officer role.

How to change an Azure SQL Database Collation

by Additional Articles

SQLServerCentral.com

Azure SQL database

In this tip we look at the steps you can follow to change the collation for an Azure SQL Database.

SQL Server Migration

by Geoff Ruble

SQLServerCentral.com

Migration

Some SQL migrations require keeping the server name, instance name, IP, and port number. Geoff Ruble shares some notes on his recent experience with a SQL Server migration.