• Adam Thurgar

SQL Server Life 1 - Constant Learning

Steve Jones from SQLServerCentral.com


asked in his editorial from the 5th of July to write 4 posts about what it is like to work in our field of SQL Server.


So here goes - post #1.

The thing that I am constantly reminded of in working with SQL Server is that you are constantly learning.

It may be a new version of SQL Server that you are moving towards (example 2016 and 2017, doing an upgrade). Every new version is packed full of new features and enhancements (and some features that have been deprecated). Some of these you may use, others you may never touch. Do you need to learn R or Python?

It could be that you are on a older version of SQL Server (2012 or 2014 etc) and you get to use a feature that you haven't used before. Maybe implementing Availability Groups?

It may be that you are looking at T-SQL code and find a new or better way to do some task. Cleaning up old code with better error handling. Creating some reports with Power BI. Better indexing

Making you environment better with alerts and better notifications, modifying the way you do backups and maintenance. Or automating some repetitive tasks with PoSH.

There is so much that you can do, as SQL Server is a massive piece of software and you can't know everything, but there is so much information out there to help you learn.

But you can learn a little bit every day and if you want to work with SQL Server you need to be ready to adapt and constantly learn.



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