Jun 17 2013

Azure First

Microsoft has been pretty clear about their commitment to the entire Azure infrastructure. The updates to Azure come out on a massively accelerated schedule. Because of this, they’re doing lots of code on lots of things that may, one day, end up in your full blown SQL Server instance, but are currently only available in Windows Azure SQL Database. This is because of that accelerated schedule. It frees Microsoft developers up to experiment a little. I saw some evidence of it the other day.

I had been working on a series of queries for the pre-conference seminar that I helped put on at TechEd (and one that I’m doing for the PASS Summit). When I write queries, I use SQL Prompt. Sorry to be plugging Red Gate products on the blog, but I happened to love Red Gate products even before I started working for the company. Prompt is one of the best. Prompt works with Azure, although you can sometimes hit errors. Anyway, I was typing up a query when I noticed a system view being offered to me that I’d never seen before, sys.database_query_store_options. I ran a SELECT against it and got this result set:

querystore

I immediately checked my SQL Server instances and did a search against the internet to see if this was just something I had simply missed. It wasn’t on SQL Server and I didn’t find a single reference to this system view in Boogle (or Ging).

What’s it mean? What do I do with it? I don’t have a clue. Heck, it could just be some obscure bit of output from Federation or something. I really don’t know. I was just excited to find evidence of ongoing development within WASD. And you see it first in Azure.

6 Comments

  • By Mike Lewis, June 20, 2013 @ 5:03 am

    I know where you’re coming from, but I personally find it massively frustrating that new functionality is released without anyone knowing. The best method for getting updates is by checking blogs, which really isn’t great.

  • By Grant Fritchey, June 20, 2013 @ 7:08 am

    yeah, no argument. I do want to know what got released and sometimes tracking it down is a little difficult. This little thing isn’t even on Boogle.

  • By Rob Volk, June 27, 2013 @ 6:27 pm

    There’s some references in SQL 2014 CTP1:

    database_query_store_options
    query_store_plan
    query_store_query
    query_store_query_text
    query_store_runtime_stats
    query_store_runtime_stats_interval
    sp_query_store_flush_db
    sp_query_store_force_plan
    sp_query_store_remove_plan
    sp_query_store_remove_query
    sp_query_store_reset_exec_stats
    sp_query_store_unforce_plan

    The sp’s are listed as extended procedures, the others are views.

  • By Grant Fritchey, June 28, 2013 @ 1:36 am

    Way to go, you just ruined my next several blog posts.

    Kidding!

    There are more than just those exposed as well. Look at views that say ‘slo*’.

Other Links to this Post

  1. Something for the Weekend - SQL Server Links 21/06/13 • John Sansom — June 21, 2013 @ 4:02 am

  2. Windows Azure Community News Roundup (Edition #69) - Windows Azure Blog — June 21, 2013 @ 8:58 pm

RSS feed for comments on this post. TrackBack URI

Leave a comment