Hi @Andreas Kreuzberg ,
This is an issue in SSMS v18.11.1, and SQL Server 2017/2019 do not exhibit this behaviour, but it affects 2016
This is a discussion from the feedback website:
https://feedback.azure.com/d365community/idea/ee71fb15-4999-ec11-a81c-000d3adfb8f5
If you want to use 2016, please try to uninstall SSMS v18.11 and try an earlier version
-------------
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.