Hi Chris!
You can set your Widows code page to UTF8:
https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/use-utf8-code-page
I believe that this would resolve your problem. As for the baseline
issue, I am not sure why would baseline or tuning profile care about the
language settings. This sounds like a bug.
On 5/2/20 1:12 PM, Chris Taylor wrote:
I *theorize *that UTF-8 plans are unsharable with clients who connect as WE8MSWIN1252 .... but SQLs that are *first *parsed by WE8MSWIN1252 connected sessions *can be *re-used by clients that come in using UTF-8 .
