This is a test on a Windows Server 2012 R2. It has 2 named instances (S1 and S2) and no default instance. S1 is MSSQL 2016 and S2 is MSSQL 2017.
Edit: Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4 (X64)
I disabledShared Memory for S2 underSQL Server Configruation Manager, SQL Server Network Configuration,Protocols for S2. I then restarted the service to apply the change. Nothing else was changed.
After the change, SSMS on local does not connect to S2 (anticipated results). However, SSMS on my desktop isnot able to connect to S2 instance either (unexpected).
Thinking I might need Shared Memory even for SSMS on my desktop; Ire-enabledShared Memory and restarted S2 services.
After reverting back, SSMS on local is able to connect to S2 (anticipated results). SSMS on my desktop still isnot able to connect to S2 instance. After some playing around, I noticed I now have to addTCP Dynamic Ports number on my SSMS - ServerABC\S2, 1444.
I thought Shared Memory will only disable connection from local. I didn't know it'll break SSMS on my desktop as well. Also, how do I fix it so I don't have to have theTCP Dynamic Ports to connect from desktop SSMS?
Thank you