Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Tony Donley

My feedback

  1. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley supported this idea  · 
  2. 35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley supported this idea  · 
  3. 39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley supported this idea  · 
  4. 1,843 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  750 comments  ·  SQL Server  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley supported this idea  · 
  5. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Additional Services  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley shared this idea  · 
  6. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Upvotes: 2

    <=-=Oct 20 2017 2:44AM=-=>

    Thank you for taking the time to post this proposal!
    Can you share more details about your use case, that describe joins required to obtain current values and also how partial temporal tables would make your development process faster?
    Regarding storage used for history data, usage of clustered columnstore index for history table reduces storage size significantly.

    Thanks,
    Mladen Andzic

    <=-=Oct 20 2017 8:07AM=-=>

    Thank you for your attention. I have updated the description to make it clear what the present options are and the drawback of each: unnecessary writes/storage, unnecessary joins, or requiring the developer to implement partial versioning themself for each such table.

    Tony Donley supported this idea  · 
  7. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tony Donley commented  · 

    I don't want to "ignore index options". I want them carefully considered and explicitly specified in source control so they are deployed consistently in every environment.

    When the only difference is the compression setting, I don't expect the engine to generate a long table rebuild. I expect and ALTER INDEX...REBUILD statement with the appropriate options.

    I would also love to see the SORT_IN_TEMPDB option honored.

    Tony Donley supported this idea  · 
  8. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Tony Donley supported this idea  · 

Feedback and Knowledge Base