Best Practice - SQL Server Connection String - Localhost versus Network Path
Posted on 2014-04-22
I have a "Best Practice" question for you. I am developing an ASP.NET website with C# code behind that connects to my SQL Server 2008 database. Both the SQL Server and the web site are hosted on the same server.
My question is this: what is the better practice when constructing the Database Connection String in the ASP.NET site? Should I use "localhost" when referring to the SQL Server, or should I use the fully qualified network path?
Is there any difference in the way the physical server handles the data request from the ASP.NET code if it's going to localhost versus the network path? If I use the network path, is the server smart enough to know that the request is directed to itself, and not route the request out the TCP/IP port, to the switch, and back to the TCP/IP port? If I use localhost, does the request get routed directly within the server without traveling to itself over the network? The advantage for me when using the fully qualified network path is that the code works on both the server, and on my development PC. However, I don't want needless traffic going out over the network if it doesn't have to on the production server.