Running SQL Server 2005 Standard Edition w/ SP1, I've encountered an issue that appears to have been resolved by limiting the amount of memory SQL Server can use.  The issue