 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / ADO.NET / March 2008Which 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. TCP is the default protocol.  Signature__________________________________________________________________________ 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) ____________________________________________________________________________________________ > Say you have a SQL Server connection string in the following format, > where MySqlServer is a server connected a local network [quoted text clipped - 10 lines] > > BOL doesn't seem very clear about this. My question is, what problem are you trying to solve? Signature__________________________________________________________________________ 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) ____________________________________________________________________________________________ > Say you have a SQL Server connection string in the following format, > where MySqlServer is a server connected a local network [quoted text clipped - 10 lines] > > BOL doesn't seem very clear about this. 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? > My question is, what problem are you trying to solve? It's been some time since I had to figure this out (over 5 years) so this is just my recollection. Signature__________________________________________________________________________ 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) ____________________________________________________________________________________________ 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? 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 >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 [quoted text clipped - 8 lines] > >> My question is, what problem are you trying to solve? 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. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.