Has anyone noticed (or hopefully fixed with a workaround) that connections to SQL from applications developed in .Net Core using the 'Core .Net SQL Data Provider' always have a blank hostname? I've noticed this when using: - DMVs such as sys.sessions, as by implication tools such as sp_whoisactive, sp_blitzwho etc - Profiler (yes I still use it) - Extended Events At first I thought it was due to how the devs had constructed their connection strings (as you can manipulate this kind of data there), but on review they seemed 'normal'. Is it due to the fact the .Net Core is platform agnostic? Is a server name a 'windows' thing? I do still see an IP address in sys.connections.
Very interesting indeed. Which version of .NET Core it is? There was an issue with the previous .NET Core version as pointed out [here] (Yes, I was helped out by the dev team :) ). We are developing new application based on .NET Core 2, but that is giving us the correct information about the HostName. :