Michael Barrett

My feedback

  1. 22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Michael Barrett commented  · 

    Agreed. It seems to optimizer is not completely "balanced" wrt. the cost of the "key lookup" in the clustered columnstore index. It should favor the clustered columnstore index directly in many cases.

    An error occurred while saving the comment
    Michael Barrett commented  · 

    Agreed. It seems to optimizer is not completely "balanced" wrt. the cost of the "key lookup" in the clustered columnstore index. It should favor the clustered columnstore index directly in many cases.

    Michael Barrett supported this idea  · 
  2. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Barrett supported this idea  · 
  3. 15 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Michael Barrett supported this idea  · 
    An error occurred while saving the comment
    Michael Barrett commented  · 

    I have tested this issue extensively, as I assumed that the native implementation of this functionality in SQL Server would be faster than my custom implementation in CLR functions. However, the native implementation proved to be around 5 times slower than my own implementation utilizing the .NET TimeZoneInfo class. I would expect the native implementation to be at least as fast as a custom implementation (that provides exactly the same functionality), and I am happy to share my implementation if interested.

Feedback and Knowledge Base