fix missing CPU column for case-sensitive SQL instances #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Adam!
I discovered that the CPU column disappears when running sp_WhoIsActive on a case-sensitive SQL instance.
I've attached the 3-character fix for it.
The rest of the changes (if any) are going to be line-endings that GitHub detected as being inconsistent.
On my branch, it changed all line-endings to Windows CR+LF, as that's what I'm using. Your mileage may vary :-)
Pro tip: on the GitHub file diff page, you can click the Cog icon and "Hide whitespace" to verify my changes are only "cpu" to "CPU".
Thanks!