Storage

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Mark TableEntity as Serializable

    There is no way to expose AzureTable data directly via WebAPI due to Serializable requirement. Unfortunately TableEntity class doesn't have that attribute and forces to create a duplicated class. Please mark TableEntity class as serializable.

    11 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 →
  2. Improve exception messages

    "An error occurred while processing this request."

    That message doesn't say anything. A suggestion would be to append the inner exception message. It makes debugging a lot easier.


    "One of the request inputs is not valid"

    That message doesn't say anything at all and I can't figure out why I get it. It's thrown on SaveChanges()

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  3. Diagnostics trace viewer in management portal

    Right now if you need to see logs, you have to query azure table WADLogsTable. This is a bit wired. I think it will be good addition to the management portal if it will show this logs in more adequate way. If it will also support search it will be even more awesome.

    16 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 →
  4. Support $filter on merger, update.

    Supporting $filter on merge and update would reduce the number of roundtrips when doing conditional mutation of an entity based on properties in addition to PK and RK.

    3 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 →
  5. Please give us Count(), TakeLast(int i), Skip(int i)

    There are many Scenarios were count is useful. Ich I write logs to Azure Tables most of the time i want to retreive the last n entries. It would be great if there would be something like TakeLast(int i) or Skip(int i) for doing something like Skip(count - take).Take(take).

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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.

    166 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. 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.

    747 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add DataSync for Windows Azure Storage so affinity groups under Traffic Manager can stay in sync

    If I choose to use Table Storage with an application that is under Traffic Manager, I would still like to maintain an affinity group for lower latency. In order to do this today I would need to syncronize data between the each of the storage nodes

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 …

    213 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 →
  11. add metadata to Table Storage tables

    It would be very useful if table could have metadata associated with them beyond just their name. A user-defined metadata entity (just like a table entity) would be awesome.

    10 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 →
  12. 35 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 →
  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.

    124 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. Allow complex types in Azure tables storage

    Currently azure tables only support simple properties and flat entities. It would be great to make it more of a "object/graph" database with the ability to cascade entities, and do deep oData queries.

    You could just make RavenDB available on azure.

    7 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 →
  15. Tool that can help migrate existing on-premise relational database to Azure table storage

    This tool should understand the on-premise relational database schema and generate equivalent tables in Azure table storage (with rowkeys as current primary keys and partitionkeys based on the indexes on the current relational table).

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Tables  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    143 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 →
  17. Table storage garbage collection

    Would be awesome to have the ability to set a data expiration/garbage collection policy on table rows. We have to write workers to delete old data now.

    4 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 →
  18. 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.

    395 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 →
  19. Make Join on the Table storage

    Allow join feature on table storage.

    15 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 →
  20. 14 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 →
  • Don't see your idea?

Feedback and Knowledge Base