Brand new machine, fresh installs of:
- Windows 10 Pro
- SQL Server 2016 Developer
- Visual Studio 2015 Community w/Update 3
- SSMS 16.4.1
Connections to my local sql server from local apps - such as SSMS.EXE are slow (several seconds) when I connect using any kind of a name, including ".", "localhost", "(local)" or the machine name, but connections are fast if I use 127.0.0.1, or ::1, or the correct numerical IPv4 or IPv6 address.
Searching the 'net for this yields a mess of results, mostly a decade or more old, but a common thread that I did see was the suggestion that this might have something to do with which IP addresses/protocols are enabled. Following that possibility, I've tried a variety of combinations of IPv4 and IPv6 addresses being enabled/disabled, and none seem to make any difference. Currently I'm running with 127.0.0.1, the real IPv4 address, the real IPv6 address and the IPv6 loopback address enabled, everything else disabled, but it's no better than any other combination I've tried. It's really annoying this way because SSMS makes new connections quite frequently, so the entire operation of the app is sluggish.
I don't believe that this is a name server (DNS or WINS or anything else) issue because local connections to other local servers, e.g. SSAS and SSRS using the same names connect quickly - only connections to SQL Server database engine are slow.
It doesn't appear to make any difference whether SQL Browser service is running or not.
Note that SSMS is not the only client app that's affected - every app I've tried behaves similarly. SSMS is just an easy example that everyone can relate to.
Any ideas?
-cd Mark the best replies as answers!