Mike Olson

My feedback

  1. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Key Vault » Certificates  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Olson supported this idea  · 
  2. 931 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    43 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →

    A common need for users of Azure Table Storage is searching data in a Table using query patterns other than those that Table Storage provides efficiently, namely key lookups and partition scans. Using Azure Search, you can index and search Table Storage data (using full text search, filters, facets, custom scoring, etc.) and capture incremental changes in the data on a schedule, all without writing any code. To learn more, check out Indexing Azure Table Storage with Azure Search: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables

    An error occurred while saving the comment
    Mike Olson commented  · 

    Azure Cosmos DB (formerly Document DB) has indexing on all properties, and they recently announced the ability to use the Azure Table API and SDKs with it (https://docs.microsoft.com/en-us/azure/cosmos-db/table-introduction), so in theory you should be able to migrate any existing tables to Cosmos without too many changes to code (in my case, I should be able to simplify a lot of code that deals with optimizing query performance).

    I have not actually worked on this, so I don't know how well it works or how complicated it is, but it may be a good path for those of us who have been struggling with Tables for a while.

    That said, I think you can also take this as a hint that significant improvements to Azure Tables are not forthcoming.

  3. 1,399 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    84 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike Olson commented  · 

    The writing's on the wall folks. It's been what, 3 years since this was supposedly added to their roadmap? When was the last time Microsoft made *any* real improvements to Table Storage, besides putting a ton of breaking changes in the SDK that required hundreds of hours of dev to support?

    Azure Table Storage is old news and is being ushered unceremoniously out the door. It's time for us to give in and move to DocumentDB, Azure SQL, or one of the dozen new storage services that Microsoft is actually putting effort into. Or just do what I've been doing and just start storing your data in flat files on Blob Storage, since for a lot of cases that's easier to code, more performant and more flexible.

    At least Microsoft isn't slowly moving us away from Cloud Services... oh wait.

  4. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike Olson commented  · 

    OK, I have removed my votes from this and moved them onto yours. Thanks for pointing this out.

Feedback and Knowledge Base