Database Lifecycle Management: Deployment and Release

So often, the unexpected delays in delivering database code are more likely to happen after the developers initiate the release process. The necessary checks and tests can turn up surprises: The handover process can expose deficiencies. With good teamwork, planning and forethought, though, the process can be made almost painless.

Defensive Programming

Learning to program defensively can prevent and catch errors early.

Proper Storage and Handling of Personal Names

As database developers, we may need to rethink the way we store and handle personal names

SQL Server 2016 Temporal Table Query Plan Behaviour

In this latest T-SQL Tuesday, Rob Farley takes a look at a couple of unexpected aspects of query plans you might observe when using Temporal Tables in SQL Server 2016.

Byte Me: Earning in the Grave

Create a SQL Server Reporting Services Report from an Analysis Services Tabular Database

Daniel Calbimonte walks through the steps to creating a SQL Server Reporting Services (SSRS) Report from an Analysis Services Tabular Database.

Changing Replication Passwords

A how-to guide for configuring replication agents after a password change

Moving Fast at Redgate

It's possible to change a software development team and dramatically improve things. Steve Jones highlights an example from Redgate Software.

Strengthening the Foundations of Software Architecture

The term 'Architecture' seems to imply a plan that you can't easily subsequently deviate from. It's true that, if you abandon software architecture, you end up with a big ball of mud, but maybe the art of software is to make change much easier by planning how to implement each feature, tackling dependency issues, splitting functionality into small discrete components and considering how they should interact with each other.

Adding Old Features?

Is Row Level Security a new feature? Or should MS work on improving old ones?