What I think is interesting in the post on the ever living engine is this sentence: "Azure automatically handles patching, backups, replication, failure detection, underlying potential hardware, software or network failures, deploying bug fixes, failovers, database upgrades and other maintenance tasks." This notes that all of these operations are completed in less than 0.01% of the database life, hence the 99.99% guarentee. While that's not 0, it's close, and more importantly, this is something that to which DBAs ought to pay attention.
These are often the tasks that many organizations will hire someone to complete. These tasks are becoming less of a time sink as organizations move to infrastructure as code or cloud computing, though they don't disappear entirely. However, these tasks are mundane, tedious ones in many cases that should be solved once and then deployed easily to multiple instances.
Azure SQL Database and SQL Server share the same code base. Most features get built and tested in Azure and then will get merged into a release for a CU or new version of SQL Server. This means that as Microsoft learns how to better build these features, they will migrate them to our boxed SQL Server versions. With success stories in Azure and strong marketing, I'd bet that more and more management will be questioning whether they need more people, or even any people to handle these tasks in the latest versions of SQL Server.
Don't panic if you're a DBA working on SQL Server 2008/RS, 2012, 2014 or other older versions. Those editions still require your time and things will change slowly for plenty of companies. They won't want to upgrade too many instances at once, especially when there are potential vendor costs as well. You will have a job for some time, and I don't think that lots of those older instances are disappearing anytime soon.
That also shouldn't mean that you rest on your existing skills and don't learn anything new. You ought to be sure you are beginning to learn more about PowerShell, Azure, automatic indexing, and more. Improve your skills and potentially give you more career options. Even if you don't change jobs, you'll enjoy the learning.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
Write, format, analyze, and refactor SQL fast with SQL Prompt
Writing SQL is 50% faster with SQL Prompt. Your SQL code can be formatted just the way you like it, you can create and share snippets with your team, and with code analysis you get suggestions to improve your SQL as you type. Download your free trial
Database migrations inside Visual Studio
Feeling the pain of managing and deploying database changes manually? Redgate ReadyRoll creates SQL migration scripts you can use to version control, build and release, and automate deployments. Try it free
I’ve been in love with the concept of a database as a service ever since I first laid eyes on... More »
Question of the Day
Today's Question (by Steve Jones):
I have built an event session in Extended Events (XE) called MyEventSession. I set this to startup when the SQL Server instance starts. It's currently running with both a file and ring buffer targets. I decide to drop this session, buit don't want to lose data from the file target. What do I need to do?
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
Expert T-SQL Window Functions in SQL Server takes you from any level of knowledge of windowing functions and turns you into an expert who can use these powerful functions to solve many T-SQL queries. Replace slow cursors and self-joins with queries that are easy to write and fantastically better performing, all through the magic of window functions. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I have this code:
DECLARE @s VARCHAR(100) = 'the quick brown fox jumped over the lazy dog' ,
@start INT = 5 ,
@len INT = 3;
SELECT STUFF(@s, @start, @len, 'xx')
Answer: the xxck brown fox jumped over the lazy dog
The STUFF command will look for a part of a string. You can specify the starting location and then the length that is deleted. Optionally, the last (4th) parameter is used to insert data. In this case, we start at position 5. This is the "q". We remove 3 characters (qui) and then insert the "xx".
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.