Azure

BACKUP TO URL was introduced as an add-on in Cumulative Update 2 for SQL Server 2012 Service Pack 1 and as a built-in feature for SQL Server 2014. I previously described this in a blog post.

We have been using this in a variety of ways from on-premises systems:

For example, it is an easy way to distribute a backup of a database to a large number of systems. Imagine you have a chain of retail stores that needs product and other reference information updated regularly. You can keep this data in a separate database at the head office, back it up to an Azure Storage account, and have each store download it separately.  This has major bandwidth and reliability improvements over other solutions such as having each store maintain a VPN connection to the head office.

2014-07-09

In the sessions that I was attending in Redmond yesterday, I was interested to see the presenter discussing the idea of having individual database files in the cloud as some sort of bizarre option that’s now available in SQL Server 2014. I don’t see it as bizarre at all. However, I see two distinct use cases that make complete sense to me:

Overcoming Drive Limitations in Azure-based SQL Virtual Machines

One of the current limitations of running SQL Server in Azure virtual machines is that you can only attach two additional data drives per CPU core, and each of those drives is up to 1 TB in size. For example, if you spin up a two core VM, you can attach 4 data drives.

2013-11-20

I had the distinct honour (honor) this week of recording a new SQL Down Under podcast with Dr David DeWitt from the Jim Gray Systems Lab at Microsoft. Anyone that has been to a PASS summit over the last few years would know that David seems to have single-handedly converted morning keynotes into must-attend events.

In this podcast, David explains his role, gives a philosophical view on where we’re at in the database industry and discusses core enhancements in SQL Server 2014.

2013-11-14

If you have followed any of the Azure website forums, you’d realize that having SSL available was one of the highest rated requests. That’s hardly surprising given the number of clients that want to use these sites for eCommerce work.

So it’s really good to see that Scott Guthrie and the team have been listening and that SSL is now available. To see the details, click on the “SSL” button in the “Learn More” area of the Azure pricing page. An FAQ is also provided.

2013-06-03

I was so glad to hear today that Azure is expanding to Australia. This helps with two remaining areas of concern that I’ve heard from a variety of customers:

• Compliance and data sovereignty (not wanting to store data outside Australia)
• Latency (previously high latency even to our nearest external data centres)

With both these concerns now disappearing, it’s time for more Australian customers to get involved with Azure if they’ve been resisting so far. 

2013-05-21

I posted the other day about a hotfix that’s needed after you apply SQL Server 2012 SP1 CU3, to still be able to open or edit SSIS projects or database maintenance plans in SSDT.

However, I found that after I applied CU3 and the hotfix, that all my stored credential details for SQL Servers was gone. That was particularly nasty for all my Azure-related logons. I had to set them up again.

2013-04-09

I recorded another podcast today with Thomas LaRock, aka SQL Rock Star.

In this show, Tom and I discussed the migration of many DBAs into architect roles, the challenges in constant learning (and useful resources for doing so), the hype around big data, the role of Windows Azure in our future, and upcoming PASS events.

It’s online now: https://podcast.sqldownunder.com

Enjoy!

2013-03-02

There has been a lot of discussion over the years about whether or not it’s a good idea to introduce new functionality in service packs (for SQL Server, the OS, and others). The concern is that it can invalidate testing, invalidate documentation, books, courseware, etc. However, it can also introduce much-needed features without having to wait for another version of the product. It’s been even-less likely that new functionality would be introduced in a cumulative update (or CU), which are basically a set of rolled-up hotfixes.

2013-01-27

One of the issues that is often raised with Windows Azure SQL Database is that you don’t get to pick the name of your server, so you end up with a bizarre name such as:

yy2l95dk1k.database.windows.net.

I can understand why the team did this. Apparently when they first set it up, they allowed you to pick your own server name, so everyone started registering Coke, Pepsi, etc. Not wanting to have yet another place for people to argue about name ownership, they quickly removed that ability. I’m glad they did.

2013-01-21

When I’ve been putting data into Windows Azure SQL Database (WASD) in the past, I’d normally been providing the dates from my own system. This week, I had the first time where I wanted to put a column default that provided a date in WASD. It suddenly dawned on me that I wasn’t sure what timezone the date would be from. As I was using the Southeast Asia data centre (in Singapore), I was presuming the value would be based on Singapore’s timezone. So it was time to find out.

2013-01-20