5 ms·I hit that too: it was a known bug in SSMS and Microsoft released an update that fixed it.by VVertigo 6y agoI hit that too: it was a known bug in SSMS and Microsoft released an update that fixed it.wdb 6y agoGood to know, thanks!