Storage

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add TableStorage LINQ query support for Select, Count and Contains

    Critical functions such as Select, Count and Contains are not currently available when querying TableStorage data.

    If I only want a total number of rows that match a certain criteria I have no choice but to retrieve the data, count it and throw it away.

    Adding support for Select would also help with heavy queries by only returning the data selected from a query.

    Contains would be useful for searching. Using the Compare function is annoying.

    1,674 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    48 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support secondary Indexes

    Need to be able to sort on something other than the rowkey

    1,380 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    83 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add ability to view Azure Table size/entity count (rows)

    Hi Mike,

    I've created this idea as suggested on the forums: http://social.msdn.microsoft.com/Forums/en/windowsazure/thread/ea18ae29-36a3-42c6-8420-877216efbd42

    One of the big challenges in adopting azure table storage over traditional SQL storage is the ability to know how much data is stored and how it is being used.

    Being able to break size/rows down by partition would be invaluable when trying to modify / optimize Partition & Row keys. (Given data doesn't always grow as we would expect, and new bottlenecks can & will emerge).

    In addition the ability to view the usage data per table / partition would be fantastic.

    Obviously there are ways of…

    1,020 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide me with full text search on table storage

    Does what it says on the tin....really need better search capabilities over azure table storage.

    928 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    43 comments  ·  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

  5. Ability to delete from Table Storage by Partition

    There is no good way to delete multiple entries in Table Storage. All you can do is delete one at a time. For logging tables this can become VERY expensive. It would be great if we had the ability to use Partitions as a way to delete logical groups of data in Table Storage in a single transaction.

    This would allow for a partitioning scheme for grouping data in units that can easily be deleted. For example, logging data in WADLogsTable or rolling tables of data captured on a given partition can be archived easily and cleaned up.

    701 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add an atomic Increment operator on table storage. See MongoDB for example.

    It's hard to create pre-aggregated counters in table storage when using multiple workers. For example, a page hit counter will have wrong counts if incremented by pulling work from a queue and updating an entity representing the page using multiple workers.

    392 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  7. Extend Table Storage Property Limit

    Currently, Azure Tables only support 255 properties (columns) on a single entity (row) and a max row size of 1MB. This should be greatly extended (e.g. 10x+), particularly since Azure does not offer Join query support. Without Join support, devs are forced to span large data structures across multiple tables. When querying the data, devs have to manage this extra complexity as well as suffer the performance penalties of querying against N tables and then performing their own post-join operation. Azure Tables scale great in one dimension (# rows), but horribly in the other (# columns). While Azure Tables should…

    189 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  8. Azure Table Storage permissions to prevent deletion

    It would be nice to be able to lock certain areas of Azure Storage to prevent operators/developers from deleting a table/container/queue by accident. Our specific need right now is for Azure Storage Tables but could potentially be for containers and queues. For example, it would be nice to lock a table to not allow deletion.

    159 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  9. Entity Framework provider for Azure Storage

    Even if clearly impossible to have all relational features implemented, a mapping between EF entities and Azure Storage tables would be great, as would simplify the migration of the data layer to Azure.

    154 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add autonumber index with identity increment column like sql server and DocumentDB

    Don't want to worry about index column like i do on the row key.
    Please add column id with auto identity increment.

    152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  11. Have a TTL on Table Storage rows, so temporary data gets deleted

    Say you are storing details about logs / orders / page views. You may not care about them after 2 weeks / 1 month / 1 year.

    To save money it would be great to have a job run daily that deletes this data when it is deemed out of data by the system designer.

    AWS has this in DynamoDB where you create a column for an expiration date on tables that will accumulate data that might be temporary by nature. When you create a row you populate this column with the timestamp in the future you want this deleted.…

    141 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support "skip" in Azure Table

    MSDN says the "take" operator is only supported for the first 1,000 rows...

    I need to access row number 5,000 in a highly partitioned storage layout. Support for "skip" is a requirement if we are to continue development.

    140 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support TCP connections to table/blob storage from within the datacenter (low latency, ultra fast).

    We have the need for ultra-fast record range retrieval from table storage (a la on-site SQL Server) from our web roles in the same data center. This is driving a data-intensive BI engine that relies on low-latency access to massive streams of data. Currently, we are looking to MongoDB to fill this gap.

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  14. Memory-Optimized off-row storage issue

    I have a problem because of data row-size of some tables greater than 8060bytes, so there was some off-row storage in internal xtp DMVs and those tables allocated a memory about 120GB.
    I alter that tables and reduce row-size to less than 8060bytes, the memory allocated to those tables reduce and the allocated memory to object_id=0 is being grow in sys.dm_db_xtp_table_memory_stats. I think The garbage collector thread cant find this orphaned object , thus it cant deallocate memory.
    another issue is 'Memory Allocated To Memory Optimized Objects' is 25GB where 'Memory Used By Memory Optimized Objects' is 62GB,

    I offline…

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Support for Lists/Arrays in Azure Tables

    Azure tables need an option to support lists/arrays for per entity instance.

    Both Google App Engine (http://code.google.com/appengine/docs/python/datastore/typesandpropertyclasses.html#ListProperty) and Amazon's simpledb both already offer this.

    It enables an effective way to relate entities without the over head of traditional SQL.

    105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  16. Azure Table Storage Events

    Allow events to subscribe to fromAzure Table Storage row create, update and delete operations. This would be liked the blob create and update today except for table storage rows.

    84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →

    Our long-term goal is to have every service within Azure publish events, however, we have yet to begin work on this one.

    As always, we’re passing the feedback along, but make sure you reach out to Storage as well so they hear your voice directly!

  17. Allow me to pay for increased entities/second from a table storage account

    Amazon's DynamoDB offers the ability to scale access to a single table, while Azure Table Storage is limited to 5000 entities/account. With Azure Federations now in place, this seems like the last remaining bottleneck for my application as it grows.

    Spreading my data across multiple accounts is a suboptimal solution because (1) it requires an additional layer of complexity in my application, (2) these accounts are not free in that I must request more of them from Microsoft myself every time I need more, (3) I'm not guaranteed to get more than 20 (5 to start, 20 if you go…

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  18. Azure table storage should have a way to set the retention policy

    There should be a way to implement a Azure table storage retention policy such that anything older than n number of days can be deleted from table storage.

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add support for gzip and/or deflate on Table Storage

    I noticed that the Storage team has gone to great lengths to reduce bandwidth usage by switching to JSON. Take this to the next logical step and add support for the Accept-Encoding header in the client libraries and have the server return content gzipped or deflated. JSON compresses quite nicely, especially if the entities returned from a query are similar, which they nearly always will be if you're querying on PartitionKey and RowKey

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  20. Like (Contains) Operator for Azure Table

    It would be very useful to use like (Contains) operator to query for rowkeys or partitionkeys, if it's not possible for partitionkeys then it could just be for rowkeys.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base