Jason

My feedback

  1. 899 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason commented  · 

    They could just use staging.[Choosen DNS Name].cloudapp.net instead of using a guid

  2. 82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Jason supported this idea  · 
    An error occurred while saving the comment
    Jason commented  · 

    I personally just stumbled across this information and I have to agree 5000 entities per second should be allowed to be scaled in someway.

    A way of handling this is to allow us to enable high load transations in the billing. A high load transaction is anything above your 5000 limit and counts seperatly than a normal transaction and is shown on your bill as such. These transactions then can have different allowance / billing details on different packages.

    The reason for enabling the feature is some people might not need this but may cause a peak load in 1 second but are happy to make the user wait while it retrys the request.

  3. 1,212 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    57 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →

    Windows Azure Websites offers the ability to have smaller deployed websites. The ability to have multiple roles on a single VM instance is still in planning.

  4. 1,692 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    49 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Jason supported this idea  · 
  5. 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

    Jason supported this idea  · 

Feedback and Knowledge Base