Post reply

Connections are not selected as documented

  • November 30, 2007 at 10:53 am

    #377275

    The following test seems to contradict documented behavior....

    1) Running SQL Server 2005 Express with Shared Memory (SM) and TCP enabled.

    2) Connect with "localhost", it connects using SM.

    3) Disable SM and restart the Server Service.

    4) Connect with "localhost", it connects using TCP.

    5) Enable SM and restart the Server Service.

    6) Connect with "localhost", it still connects using TCP!!

    To restore a SM connection, the only way that I have figure out is...

    7) Disable TCP and restart the Server Service.

    8) Connect with "localhost", it connects using SM.

    And then restoring TCP does not change the connection

    9) Enable TCP and restart the Server Service.

    10) Connect with "localhost", it still connects using SM.

    If you run steps 1 - 6 but skip #4, step #6 will connect with SM. So one concludes that the TCP connection is somehow "sticky".

    Any ideas on how to force a shared memory connection in step #6?

    Z

  • December 4, 2007 at 9:58 pm

    #757207

    Shared memory is a local protocol and can be used only in the machhine where the sql server is running. you can't connect to server using this protocol from a client machine.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply