0

I created an alias named "ProductServer" to point to a SQL Server 2008 R2 named instance on my local machine. I'm trying to upgrade that to point to SQL Server 2014 named instance. I used SQL Server Configuration Manager to change the entry to point to the correct instance, and it shows correctly. The Client Network Utility confirms the change is configured correctly.

When I connect to ProductServer from SSMS, after restarting the machine, it still points to the wrong instance (still 2008R2). Any ideas why it won't map to the correct one?

  • 2
    Did you change both 32-bit and non-32-bit aliases? – Antoine Hernandez Nov 4 '16 at 22:41
  • @AntoineHernandez I'm on windows 10, in MMC, I brought in both instances of configuration manager and they match. – Brian Mains Nov 9 '16 at 18:45
  • These two instances are on the same machine (my local machine), but I only changed the named instance - maybe it's pointing to the default instance? – Brian Mains Nov 9 '16 at 18:48
  • Normally you have the SQL Native Client 10.0 Configuration (32bit) and also the SQL Native Client 10.0 Configuration, usually in the third and fifth positions, respectively. You checked both of these within the SQL Server Configuration Manager Plug-in within MMC? – Antoine Hernandez Nov 9 '16 at 18:50
0

Your local PC has some network stuff cached. Try

ipconfig /flushdns

What is in your "hosts" file on your PC?

c:\Windows\System32\Drivers\etc\

hosts is the name, no file type at all. Use Notepad or notepad++

| improve this answer | |
  • The issue is with my local machine, so how is the hosts file going to help here? ipconfig didn't work... The main difference between the two is the alias is pointing to the same location, just to a different named instance... – Brian Mains Nov 9 '16 at 18:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.