title: Does large SQL Server Memory Usage cause errors?
body: <p>Just started getting a bunch of errors on our C# .Net app that seemed to be happening for no reason. Things like System.IndexOutOfRangeException on a SqlDataReader object for an index that should be returned and has been returning for a while now.</p>
  
  <p>Anyways, I looked at the Task Manager and saw that sqlservr.exe was running at around 1,500,000 K Mem Usage. I am by no means a DBA, but that large usage of memory looked wrong to me on a Win Server 2003 R2 Enterprise with Intel Xeon 3.33Ghz with 4GB ram. So I restarted the  SQL Server instance. After the restart, everything went back to normal. Errors suddenly stopped occurring. <strong>So does this large main memory usage eventually cause errors?</strong></p>
  
  <p>Additionally, I did a quick Google for <a href="http://www.google.com/search?q=high+memory+usage+mssql" rel="nofollow noreferrer">high memory usage mssql</a>. I found that if left to default settings;  SQL Server can grow to be that large. Also, found a link to MS about <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;321363" rel="nofollow noreferrer">How to adjust memory usage by using configuration options in SQL Server</a>.</p>
  
  <p>Question now is...<strong>how much main memory should SQL Server should be limited to?</strong></p>