• Adam Thurgar

Using new features

In August I blogged about using the new SQL Server 2016 temporal tables for a client requirement. It did everything they required and more. The time machine worked great. But the I started questioning the client requirements and what where thinking of delivering. This is an organisation with developers, but no full time trained DBA. A few accidental DBA's. Who could or would be able to understand temporal tables moving forward? Would it just be forgotten until one day it broke. Sometimes you need to think about who is going to maintain this environment into the future. After discussions with the team we decided that temporal tables were, in this case, overkill. We went with a more basic, simple solution (using the KISS principle) and better/easier for the client.

3 views0 comments

Recent Posts

See All

Cardinality estimator

Recently I was asked by a software vendor to review a particular query that ran in under a second on a SQL Server 2014 installation at a compatibility level of 110 (SQL Server 2012), but when run unde

Index fragmentation

A law firm client, occasionally has issues with their legal software, that is provided by the global leader in this field. The response from the software provider is always the same - you have index f

Deleting large amounts of data

I had a client call me about wanting to delete a large amount of data from their database. They knew what tables they wanted to delete from. They also knew that deleting large amounts of data causes t