I am running SQL 2012 on Windows Server 2008. I have set the maximum allowed memory for SQL Server. Also, I've installed all of the latest SQL 2012 updates.
I have noticed that in task manager that the physical memory in use for the entire server is very slowly growing over time by approximately 1% a week. The SQL Server memory usage in task manager does not appear to be growing but I suspect that this is not accurate. Meaning, I believe that this process is leaking memory that is not able to be tracked by Task Manager.
Has anyone else encountered this issue? Are scheduled reboots an expected practice these days? Is Windows Server 2012 any better?
SQL Server is a memory hog and will eventually use the maximum allowed memory. This is normal and not a memory leak. Task Manager does not properly display the SQL Server memory consumption but PerfMon does. It's the Total Server Memory counter object in the Memory Manager counter.
There is no reason to schedule a reboot or restart of the service.