You may experience a decrease in overall system performance when you are copying files that are larger than approximately 500 MB in Windows Server 2003 SP1 or in Windows Server 2003 SP2
This affects all editions, x32 and x64, windows 2003.
The knowledge base article states the following symptoms:-
When you copy files that are larger than approximately 500 MB on
a computer that is running Microsoft Windows Server 2003 Service Pack 1 (SP1)
or Windows Server 2003 Service Pack 2 (SP2), you may experience a decrease in
overall system performance although the copy job is still running correctly.
· Your desktop and the programs that are running on the computer may stop responding.
· The mouse may stop responding.
· Working set of certain applications, such as SQL Server, may be trimmed or paged out.
However, you may find file copies just never seem to complete and fail for no obvious reason, robocopy may suffer in this manner.
The knowledge base cause is listed as follows:
· What this means is if you’re copying a sql backup file from a fast array to a slow array, or even single disk you may tun into problems.
· This can be affected by the setting of the large system cache and can be a real problem on x32 systems.
· There is a “hotfix” for sp1 but I’d rcommend always applying sp2, anyway which ever route you follow you have to make this registry change
· Although I do not know for certain it is likely you must enter the registry key with the exact case as shown.
The knowledge base fix is as follows: ( images added for clarification )
After you apply this fix or after you install Windows Server 2003 SP2, you must add the SystemCacheDirtyPageThreshold registry entry to change the default behavior. To do this, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then right-click the following registry key:
3. Point to New, and then click DWORD Value.
4. Type SystemCacheDirtyPageThreshold, and then press ENTER.
5. Double-click SystemCacheDirtyPageThreshold.
6. In the Value data box, type 0x20, and then click OK.
o "0x20" corresponds to a decimal value of 32 MB.
o The range of values for the SystemCacheDirtyPageThreshold registry entry are as follows:
value: Total physical RAM in MB divided by 64
7. Exit Registry Editor.
For SQL Server I’d suggest the minimum values are more appropriate, expecially for x32.