Lajos Marton

My feedback

  1. 609 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  2. 288 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  3. 301 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Web Apps » Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  4. 329 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Web Apps » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  5. 1,804 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    70 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →

    We’re excited to announce that we are making this a lot easier with our preview of Autopilot. With Autopilot, Azure Cosmos DB will automatically manage and scale the RU/s of your containers based on the usage. This eliminates the need for custom scripting to change RU/s and makes it easier to handle bursty, unpredictable workloads.

    You can try out Autopilot in your Cosmos accounts by going to the Azure Portal and enabling the feature in the “Preview Features” blade.

    Lajos Marton commented  · 

    The direction is good, but I would need more lower throughput numbers. As now the minimum is 10% and the minimal maximum output is 2000. But what if, I would need minimum 10 and maximum 100? My main issue is with Cosmos DB that is too expensive for low loads in DB.

    Lajos Marton supported this idea  · 
  6. 974 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  70 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  7. 292 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 72

    <=-=Mar 10 2016 11:26AM=-=>

    It’s a shame that this was submitted as just a “suggestion”. It should actually be listed as a “bug” because there’s only a comparatively small set of use cases where enumeration of the result set of elements is not important.

    <=-=Mar 11 2016 12:47PM=-=>

    I agree that an order column is required; one example use case is where two lists are passed in, and ordinal positions in one list correspond to positions in the other.

    <=-=Mar 11 2016 3:12PM=-=>

    Please see the related suggestion: STRING_SPLIT needs “RemoveEmptyEntries” option, like String.Split in .NET ( https://connect.microsoft.com/SQLServer/feedback/details/2462002/ ).

    <=-=Mar 12 2016 12:02PM=-=>

    This kind of function is primarily needed for de-serializing previously serialized arrays of values of any type format-able as text.
    I therefore recommend to have the result set of this function work excellent with this use-case.

    With de-serialized arrays there is a need to…

    Lajos Marton supported this idea  · 
  8. 256 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 127

    <=-=Jun 23 2015 8:37AM=-=>

    I’m the first to post a useful comment. This must make me special.

    Seriously though, this would be an excellent solution to having to create a new “scratchdb” to hold my interim ETL data. This would be a major plus in simplifying design of a high performance app.

    <=-=Jul 3 2015 5:04AM=-=>

    In 2014, memory optimized tables, and delayed durability can be used help mitigate these Issues. However neither of this are always completely viable solutions. Brent’s proposed solution is likely the simplest way to achieve this with the least amount of unwanted impact. It is important to note that other platforms implement similar functionality as well. Notably Oracle.

    <=-=Nov 29 2016 3:58PM=-=>

    There are so many good things about this suggestion. I am amazed that SQL does not have the capability to turn off logging for certain tables that you define as no…

    Lajos Marton supported this idea  · 
  9. 337 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 8

    <=-=Mar 5 2017 2:42PM=-=>

    Thanks for this idea. This is a valid requirement and I hope that it will get more votes. Currently we cannot confirm when it will be added, but it is in our backlog.

    <=-=May 22 2017 5:03AM=-=>

    would like it very much, particularly since you already have the CONCAT / GREATEST() a variable number of paramenters and does something with it…

    <=-=Jun 5 2017 12:31PM=-=>

    GREATEST / LEAST functions would be fantastic addition.

    <=-=Nov 14 2017 3:42PM=-=>

    The workarounds using CROSS APPLY or CASE expressions are difficult to manage and read. I’d love to see these implemented.

    Lajos Marton supported this idea  · 
  10. 36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton shared this idea  · 
  11. 2,831 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    91 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Cosmos DB now supports GROUP BY queries! With GROUP BY, you can run queries that group your results according to the values of one or more specified properties. This feature is currently supported in Data Explorer, JavaScript SDK 3.4, and .NET SDK 3.3. Support for other SDKs will be available later this year.

    Lajos Marton supported this idea  · 
  12. 81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  3 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  13. 503 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  14. 441 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  15. 3,852 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    132 comments  ·  Azure Cosmos DB  ·  Flag idea as inappropriate…  ·  Admin →

    Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.

    Update.

    The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
    github.com/azure/azure-cosmos-dotnet-v3

    We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.

    Once that is released we will mark this feature as complete.

    Thank you for your patience and votes.

    Lajos Marton commented  · 

    Finally, it will worth the money.

    Lajos Marton supported this idea  · 
  16. 198 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
    Lajos Marton commented  · 

    My most painful point is the 32Kb limit of property size. If I use it as a key - value store (and why not, actually it is), then I can't use the 1mb row limit, if I have only one key and one value in a row and value must be maximum 32Kb what is very tiny :(

  17. 4,299 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    96 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  18. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton shared this idea  · 
  19. 128 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Networking » Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
  20. 182 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Lajos Marton supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base