title: Separate application server and database server
body: <p>I was wondering what to do if an application has a heavy load of database queries.</p>
  
  <p>I am using a Microsoft SQL Server 2012 and currently (development time) I am running the SQL Server on the same machine as the ASP.NET application. Everything is fine. The connection is made via loopback interface (localhost), so there is no speed impact at all. There is no physical network.</p>
  
  <p>What happens if the RAM usage is very high because of the SQL Server in production mode? Would it be better to separate the application machine from the database machine?</p>
  
  <p>But if so, the connection has to be done via a real network interface instead of a pseudo loopback interface. Is there any speed impact in this case? Does it result in a latency because of the introduction of a physical network?</p>
  
  <p>Typically I would rent 2 root servers from a hosting provider. One for the application, one for the database with huge ram. How do they communicate with each other? Do both have local IP adresses to get a fast interconnection? Both machines from the same provider.</p>
  
  <p>Thanks in advance</p>