Afaik I know the MGMT studio is sluggish on x64 as it's 32 bit.
This might have the same issue for your machine.
That's a good lead. I am curious about these details. Do you have an article that references these issues, or maybe how to mitigate them?
Also if you are on the server it will use shared memory.
I am able to force the use of TCP/IP on my local server by providing the IP address or the specific Port number when connecting.
IP_ADDRESS\INSTANCE_NAME = TCP
IP_ADDRESS,PORT_NUMBER = TCP
.\INSTANCE_NAME = Shared Memory
.,PORT_NUMBER = TCP
SERVER_NAME\INSTANCE_NAME = Shared Memory
SERVER_NAME,PORT_NUMBER = TCP
(local)\INSTANCE = Shared Memory
(local),PORT_NUMBER = TCP
Note: my client protocol priority was not changed from the default order -> Shared Memory first, TCP/IP second, Named Pipes third
You can check your transport with this query after connecting:
WHERE session_id = @@spid ;
__________________________________________________________________________________________________There are no special teachers of virtue, because virtue is taught by the whole community. --Plato