Why can I still use named pipes to connect to SQL Server even if it's been disabled? I'm on SQL Server 2016 doing the testing. I have recorded my operation in this youtube video: https://www.youtube.com/watch?v=4lvkbwsspZc Hope someone can point me the right direction.
asked Nov 16, 2016 at 11:39
Add a comment
|
1 Answer
Check the SQL Server error log for the named pipes provider messages. With named pipes enabled, you should see messages like those below and be able to connect both locally and remotely over named pipes:
Server local connection provider is ready to accept connection on (named pipe)
Server named pipe provider is ready to accept connection on (named pipe)
With named pipes disabled, you should see only local connection provider message(s). You'll still be able to connect locally via named pipes (over shared memory) but not remotely via named pipes.
answered Nov 16, 2016 at 12:13
-
Thanks Dan, It seems that you are correct. I only see local connection information in my error log. But I have two:
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].Is this behavior documented in books online? I can't find them anywhere. How do you know it? Commented Nov 16, 2016 at 12:22 -
3@OgrishMan, I don't know if/where this is documented but shared memory is a local named pipe implementation. I learned this recently from the Microsoft contact Erland mentioned in an MSDN forum answer: social.msdn.microsoft.com/Forums/sqlserver/en-US/… Commented Nov 16, 2016 at 12:28