Welcome to BlobEater

Featured

I am passionate about using Microsoft Technology to maximise business benefit. Specializing in the Data Platform – SQL server, Azure SQL DB, Azure SQL DW, elastic pools, managed instances etc.

As a great leader once said “We all need people who will give us feedback. That’s how we improve”.  So any questions/ feedback – please Get In Touch

Copyright ©  in accordance with the Copyright, Designs and Patents Act 1988. All rights reserved. You are free to use any of the content here for personal use but need permission to use it anywhere or by any means (electronic, mechanical, photocopying, recording or otherwise).

 

Blog Series: Azure Cloud “Fear” Busting

Featured

I have decided to do a 4-part series on Cloud “Fear Busting” scenarios. Why? Over the past few years working with the cloud (Azure) I have come across 4 main “fears” or “concerns” that stand out in my mind that people have highlighted when adopting cloud technology for their database tier. Each “fear” with form a blog post where I am hoping that after reading each post you will be “less” fearful. More specifically I will be looking at these topic areas:

  • I have security fears for SQL Database.
  • Performance Issues that I faced – Learn from my mistakes.
  • There is no going back – can I get the data back?
  • I’m a DBA – Will I lose control?

Series Link Here.

Azure SQL DB – Failed to update database because the database is read-only

Quite an interesting  situation I found myself in where I was perplexed for about 5 minutes. I was connected to an Azure SQL Database where I was configuring some users where then I executed a query and was presented with the following message:

Msg 3906, Level 16, State 2, Line 2
Failed to update database “testdb” because the database is read-only.

Continue reading

Auto-Scaling Azure SQL DB

When I was presenting my Azure SQL Database session at DataRelay (used to be SQLRelay) I was asked (over coffee) about auto scaling capabilities. Quite simply there is nothing out of the box to achieve this. The idea of auto scaling would be good where you would need a burst to fulfill higher demand in terms of workload for a time duration, you know, something like “end of the day, Friday night sale” for your database.

Continue reading

Giant Azure SQL Databases

Okay it is not really called Giant Azure SQL Database but its close. There is a new public preview vCore service tier called Hyperscale. The architecture behind this is very different to that of a Standard tier SQL database (as an example).  What drives this concept? Flexible storage architecture where you can scale out the storage as your database grows (up to the 100TB mark).

Continue reading

Accidentally deleted an Azure SQL DB?

Okay honestly I have done this once. I have deleted Azure SQL Databases and then try and find the quickest way to recover. The Azure portal is actually pretty good when it comes to deleting resources, for example it will usually ask you to re-type the name of the resource to confirm deletion, so you can tell what a bad mistake I made.

Continue reading

Hello Cloud Goodbye DBA

No, not quite. I have had many interesting conversations around this topic and I don’t think (personal opinion) that DBAs will disappear from the world of IT. It will definitely change, the so-called “production DBAs” affected the most. With Azure SQL Database (and other company offerings – think Oracle Autonomous DB) you will need to adapt (both short term and long term) some argue with me that the long-term looks harder to predict for DBAs which is true so I can’t talk about that. I mean for example how good will automatic tuning get? Better than the average DBA? I am looking at things from a short-term perspective. What tasks are expected  of you to carry out in this new world? Well, this is from experience.

Continue reading

Moving an Azure SQL Database across Resource Groups

In my mind there are a couple of ways to move a database across resource groups. They vary from scripting to just using the Azure portal. I am going to use the Azure portal and do the following.

  1. Export a database in resource group X to a storage account Z.
  2. Import the file from the storage account Z into a database that is in resource group Y.

It’s just like a “backup and restore” strategy, all with the assumption that you are working within the same subscription ID.

Continue reading