Storage

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Email Notifications of Storage/Capacity

    have email notifications of storage limit or service capacities. Recently ran out of space w/ no warning...

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. antivirus for blob storage

    Ability to scan files in blob storage.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Blobs  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please fix standalone Azure Storage Explorer to not change DateTime fields

    I'm using the standalone Azure Storage Explorer with a Table Storage database and when I double-click a row to see the fields and then click Update, Azure Storage Explorer changes the DateTime fields even though I didn't make any changes. It's adding 6 hours each time.

    It's easy to reproduce: open a table with a DateTime field, double-click a row, don't change anything - just click Update. Then open the same row and you'll see the time has changed. Click update again. Open the row again - the time changed again (adding 6 hours each time)!

    While searching for help…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Storage Explorer  ·  Flag idea as inappropriate…  ·  Admin →
  4. highlight how to disable Nagle's algorithm in your performance optimization MSDN articles

    The MSDN article that describes Nagle's algorithm (http://msdn.microsoft.com/en-us/library/windowsazure/hh697709.aspx) should highlight the performance gains from disabling Nagle's algorithm.

    In our case, disabling that algorithm yielded an order of magnitude improvement in latency (from 300 to 30 ms). This is a vital piece of information that is not highlighted in performance optimization documentation for Azure.

    It may even be worthwhile to consider disabling Nagle's algorithm by default, or provide some default configuration examples that remark on this algorithm.

    1 vote
    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 →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base