Using named pipes

We run Analysis Services on the same server as an asynchronous connection-string-d-lockcopy of  SQL (mainly for licensing reasons). We have been having problems when processing the cube that it drops the TCP connection to
SQL. It was suggested that we use Named Pipes instead of TCP connections. We don’t want to turn off TCP completely, so how do you tell a connection to use named pipes?

Turns out it’s pretty easy. In the connection string we just need to add a np: to the start of the server name. So to connect to your local database, your connection string looks something like this:

Server=np:(local); Database=DatabaseName; Trusted_Connection=True; Encrypt=True; Connection Timeout=30;


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a website or blog at

Up ↑