I'm running SQL Server 2012 (x64) on a Windows 10 (x64) machine with 64GB of RAM. I've allocated 32000MB to SQL Server. When running a Restore with NORECOVERY, RAM hardly gets used and the job takes upwards of 17 hours. I have what seems to be a near identical setup on a different reporting server that runs the job in ~4hours.
I've taken a look at some perfmon counters and noticed that while target server memory is at 32GB, total server memory hovers around 1GB. From what I understand, this means there is memory pressure on the server, however, total RAM usage on the box stays between 4%-6%.
Any ideas on what could be causing the issue? We've all seen SQL gobble up memory, interesting that I can't get this instance to take any.
FWIW, i've also added the NT Service/MSSQLSERVER to 'Gpedit - lock pages in memory' with no improvement.
I'm starting to lean towards bad RAM or MOBO. However, Windows and BIOS seem to see the RAM fine, and a memtest comes back clean.
Please tell me I'm overlooking something dumb.
Asked by KCZAR
(1 rep)
Jul 29, 2021, 05:54 PM