My feedback

  1. 30 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  12 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Denis commented  · 

    Hi Stephen,

    thanks you for your response and sharing this strange workaround. It seems to work indeed! I have tested one way, now need to proove if it makes symmetric key fully interoperable with previous SQL Server versions. What about future versions? :)

    Interesting what does this undocumented trace flag actually do? Does it force the older SHA1? If so, I wonder why there is no such <algorithm> - option for SHA by creating a master key / symmetric key?

    I've not found trace flag (TF) 4631 in the Microsoft list:

    Denis commented  · 

    Are there any solution? Server 2017 CU4 (version 2017.140.3022.28) still the same problem

    I wonder how many people / companies use unencrypted data on SQL server... and do not have such problems with encryption :)

    Denis supported this idea  · 

Feedback and Knowledge Base