Adding up to the answer above, it is the issue that is resolved after SQL Server 2012 release. Thus, updating the SSMS to the 2014 or higher versions genuinely resolves the issue.
Elvin Aghammadzada
- 99
- 3