We have a server transfering a 50 GB database daily via file system, and attaching. On new servers just put in place, it is causing the memory to be trimmed, causing poor performance, and worse, not allowing logins (which shuts down the application for selling products on the web).
Per we altering the Registry entry for SystemCacheDirtyPageThreshold so it trims at a different value (i.e. 1 GB). One thing we're unsure of is whether it would provide better performance to have memory paged to disk at small intervals (i.e. 32 MB, or 512 MB, etc), or if it'd be better to let it pile up in memory a bit longer, and have larger writes to disk separated further apart (i.e. every 1 or 2 GB).
Since this is a 16 GB memory server, by default, it was already set to 8 GB, which was robbing SQL Server of half its memory.
Does anyone have any knowledge or experience with this? Would it be better to stick with 1 or 2 GB values, or smaller ones?
-Ovatvvon :-Q
Per we altering the Registry entry for SystemCacheDirtyPageThreshold so it trims at a different value (i.e. 1 GB). One thing we're unsure of is whether it would provide better performance to have memory paged to disk at small intervals (i.e. 32 MB, or 512 MB, etc), or if it'd be better to let it pile up in memory a bit longer, and have larger writes to disk separated further apart (i.e. every 1 or 2 GB).
Since this is a 16 GB memory server, by default, it was already set to 8 GB, which was robbing SQL Server of half its memory.
Does anyone have any knowledge or experience with this? Would it be better to stick with 1 or 2 GB values, or smaller ones?
-Ovatvvon :-Q