Which protocol is used if not specified in connection string?

Say you have a SQL Server connection string in the following format,
where MySqlServer is a server connected a local network

"data source=MySqlServer; Initial Catalog=MyDatabase; Integrated
Security=FALSE; User ID=MyUserName; Password=MyPassword; Pooling=True;
Connect Timeout=50"

I am wondering what protocol (tcp, named pipes, etc.) would be used
with a connection string in this format.

If MySqlServer supports both named pipes and tcp, is the protocol
indeterminant? Or is there a default protocol?

BOL doesn't seem very clear about this.

William
Fri Feb 08 12:53:53 CST 2008

TCP is the default protocol.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Ira Gladnick" <IraGladnick@yahoo.com> wrote in message
news:6450b3d8-665e-43ce-bb33-f58093576f85@c4g2000hsg.googlegroups.com...
> Say you have a SQL Server connection string in the following format,
> where MySqlServer is a server connected a local network
>
> "data source=MySqlServer; Initial Catalog=MyDatabase; Integrated
> Security=FALSE; User ID=MyUserName; Password=MyPassword; Pooling=True;
> Connect Timeout=50"
>
> I am wondering what protocol (tcp, named pipes, etc.) would be used
> with a connection string in this format.
>
> If MySqlServer supports both named pipes and tcp, is the protocol
> indeterminant? Or is there a default protocol?
>
> BOL doesn't seem very clear about this.

William
Fri Feb 08 12:54:33 CST 2008

My question is, what problem are you trying to solve?

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Ira Gladnick" <IraGladnick@yahoo.com> wrote in message
news:6450b3d8-665e-43ce-bb33-f58093576f85@c4g2000hsg.googlegroups.com...
> Say you have a SQL Server connection string in the following format,
> where MySqlServer is a server connected a local network
>
> "data source=MySqlServer; Initial Catalog=MyDatabase; Integrated
> Security=FALSE; User ID=MyUserName; Password=MyPassword; Pooling=True;
> Connect Timeout=50"
>
> I am wondering what protocol (tcp, named pipes, etc.) would be used
> with a connection string in this format.
>
> If MySqlServer supports both named pipes and tcp, is the protocol
> indeterminant? Or is there a default protocol?
>
> BOL doesn't seem very clear about this.

Ira
Wed Feb 13 14:42:47 CST 2008

The sysadmin in my shop seemed to be under the impression that if TCP
was not specified in the connection string, then named pipes would be
the default protocol. So it was requested that we change connection
strings to explcitly specify TCP as the protocol.

I was curious if named pipes actually was the default. Did some
searches, but couldn't seem to find a solid reference one way or the
other.

Is it documented somewhere that TCP is the default?


On Feb 8, 10:54=A0am, "William Vaughn" <billvaNoS...@betav.com> wrote:
> My question is, what problem are you trying to solve?
>

William
Wed Feb 13 15:10:03 CST 2008

It's been some time since I had to figure this out (over 5 years) so this is
just my recollection.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Ira Gladnick" <IraGladnick@yahoo.com> wrote in message
news:c85c7332-d3f8-4c01-b631-a99a5e409b82@l1g2000hsa.googlegroups.com...
The sysadmin in my shop seemed to be under the impression that if TCP
was not specified in the connection string, then named pipes would be
the default protocol. So it was requested that we change connection
strings to explcitly specify TCP as the protocol.

I was curious if named pipes actually was the default. Did some
searches, but couldn't seem to find a solid reference one way or the
other.

Is it documented somewhere that TCP is the default?


On Feb 8, 10:54 am, "William Vaughn" <billvaNoS...@betav.com> wrote:
> My question is, what problem are you trying to solve?
>

Mary
Fri Feb 15 13:25:33 CST 2008

How did your sysadmin configure the server? Did you see the BOL topic,
Choosing a Network Protocol
(http://technet.microsoft.com/en-us/library/ms187892.aspx)? You can
see how they're prioritized for your server by using the SQL Server
Configuration Manager.

--Mary

On Wed, 13 Feb 2008 12:42:47 -0800 (PST), Ira Gladnick
<IraGladnick@yahoo.com> wrote:

>The sysadmin in my shop seemed to be under the impression that if TCP
>was not specified in the connection string, then named pipes would be
>the default protocol. So it was requested that we change connection
>strings to explcitly specify TCP as the protocol.
>
>I was curious if named pipes actually was the default. Did some
>searches, but couldn't seem to find a solid reference one way or the
>other.
>
>Is it documented somewhere that TCP is the default?
>
>
>On Feb 8, 10:54 am, "William Vaughn" <billvaNoS...@betav.com> wrote:
>> My question is, what problem are you trying to solve?
>>

Ira
Fri Mar 07 18:39:13 CST 2008

Got it, thanks to all.

This is actually a SQL Server 2000 installation, so the SQL Server
Network Utility rather than the SQL Server
Configuration Manager.