August 2009
Intermediate to advanced
464 pages
13h 59m
English
In almost all cases, the best configuration setting is the default. Any change should be based on sound advice, and tested for performance and stability in an accurate load-testing environment before implementation in production.
The reason for a configuration change is sometimes easy to forget. To assist in future troubleshooting, each configuration change should be recorded in a change log with at least the following details: date and time of the change, person executing the change, script location (if change was script based), and the results of the change (observed performance, any errors, etc.).
In a 32-bit platform, the /3GB switch (or BCDEdit/increaseuserva) can be used to enable ...
Read now
Unlock full access