I have a SQL 2012 SP1 running on win 2012 R2. I have 80 GB for the machine. No matter WHAT I set the max ram to on SQL, it fills up the entire machine and crashes. I am currently trying to run the following to prevent this from happening, yet I do not think this is really working. EXEC master.dbo.sp_executesql N'DBCC DROPCLEANBUFFERS' EXEC master.dbo.sp_executesql N'DBCC FREESESSIONCACHE' EXEC master.dbo.sp_executesql N'DBCC FREEPROCCACHE' EXEC master.dbo.sp_executesql N'DBCC FREESYSTEMCACHE ([ALL])' EXEC master.dbo.sp_executesql N'DBCC FLUSHPROCINDB( 7 )' A long time search of this has revealed that this happens and the answer is "more ram". My database is 17 Gigs. This appears to be a lot for this. The 2012 server is using a linked server to the 17 gig database. The 2012 server is being hit by Crystal reports that simply use views to the linked server and database (sql 2005 not an issue). Is there some type of formula where you can decide on ram? I have a lot of individals asking why is the database cached 4 times and still wanting more? I have optimized for adhoc queries and this has produced little results.