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