$ 0 0 Problem still seen in 3.3.6690.40101, at least when using it within SSMS 2017 (I haven't checked older versions of SSMS)