Solved

Best Practice - SQL Server Connection String - Localhost versus Network Path

Posted on 2014-04-22
3
703 Views
Last Modified: 2014-04-22
Experts,

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.

Thoughts?

Thanks!

John
0
Comment
Question by:John Parker
  • 2
3 Comments
 
LVL 82

Accepted Solution

by:
Dave Baldwin earned 500 total points
ID: 40016131
'localhost' does not get routed over the network.  Generally the recommendation is to use 'localhost' when you don't need remote access and of course, kill or turn off any remote access in the SQL Server configuration.  That will 'improve' security by limiting access.

If you use the FQDN, the request will go thru the network for resolution even if it is for the local machine.  Only you would know if these things are actually important.  If the traffic is low and the network is not accessible by the 'outside world', then it doesn't matter much.
0
 

Author Closing Comment

by:John Parker
ID: 40016413
Awesome!  Exactly what I was looking for.  Sounds like it will be cleaner, safer, and better on my network to update my connection strings to use local host when deploying the site to the server.  Thanks!
0
 
LVL 82

Expert Comment

by:Dave Baldwin
ID: 40016416
You're welcome, glad to help.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Problem Hi all,    While many today have fast Internet connection, there are many still who do not, or are connecting through devices with a slower connect, so light web pages and fast load times are still popular.    If your ASP.NET page …
A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…
This video explains how to create simple products associated to Magento configurable product and offers fast way of their generation with Store Manager for Magento tool.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now