Comments on: SQL Server Diagnostic Information Queries for July 2018

By: ethan klitz

ethan klitz — Mon, 23 Jul 2018 17:06:10 +0000

You may not visually “see” anything as SSMS renders as white space. I may have sent you down the wrong path saying I got red squiggly in SSMS, this happened because I open the DMV script in vscode and copy to my production server SSMS.

If you have SQL Operations Studio or VSCode you can visually see the non-ascii characters.

For what it’s worth the characters exists in the 2017 DMVs too.

Using the regex I mention above do you see the characters I’m talking about?

By: Glenn Berry

Glenn Berry — Mon, 23 Jul 2018 16:53:15 +0000

I still don’t see anything amiss in SSMS. I just pasted the code for that query from the SQL Server 2017 set to the SQL Server 2016 SP2 set.

By: ethan klitz

ethan klitz — Mon, 23 Jul 2018 16:25:23 +0000

In reply to Glenn Berry. if you paste this [^\x00-\x7f] into SSMS find and click the .* regex search you can see all the non-ascii characters. looks like the ones in VLF query are no break spaces

By: Glenn Berry

Glenn Berry — Sat, 21 Jul 2018 21:20:31 +0000

In reply to ethan klitz. I don't see anything like that when I open that set in SSMS 17.8.1.

By: ethan klitz

ethan klitz — Fri, 20 Jul 2018 17:51:18 +0000

Glenn, the july version of SQL 2016 SP2 has a bunch of replacement unicode characters. Specifically look at the (Query 34) (VLF Counts) in an editor like vscode or SSMS get red squigly’s (renders as space in notepad).