Plan for failure in automated deployments

Failures happen with manual and automated releases, they are a fact of life. Make sure you know how and when to rollback failed deployments

The End of 2015

Steve Jones looks back at 2015 and the year we had as data professionals.

Actual “Number of Rows Read” in SQL Server Execution Plans

Kendra Little takes a look at the upcoming SQL Server 2016 'Number of Rows Read' feature in action.

Byte Me: Three Wise Men

Best Practices For Deleting SQL Server Data

Inevitably there comes a time where some backend data cleanup needs to be done. Ben Snaidero shares some best practices to follow when deleting data.

Sharing Code

Most people blog to share something they've done, and hopefully with the idea that someone else will learn and benefit from it. Steve Jones is happy to share code, but not everyone seems to be in agreement. In any case, you ought to respect the author's wishes.

Declarative SQL: Using UNIQUE Constraints

In SQL, you can express the logic of what you want to accomplish without spelling out the details of how the database should do it. Nowhere is this more powerful than in constraints. SQL is declarative, and Joe Celko demonstrates, in his introduction to Declarative SQL, how you can write portable code that performs well and executes some complex logic, merely by creating unique constraints.

Is Change Coming?

In the final Database Weekly of 2015, Steve Jones looks at a CIO's column on workplace change.

Read-Only Routing for Non-Microsoft Clients

An alternative read-only routing technique for non-Microsoft clients.

Why Use the Principle of Least Privilege?

SQL Injection isn't special code. It consists of regular, valid T-SQL that is unexpected by the application. Steve Jones notes that using the principle of least privilege can help to limit the damage from SQL Injection if the application fails to properly check input.