存储变化和设计考虑-Microsoft.ppt

* ? 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. * * ? 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. * Do not make changes right away into the database so multiple updates can occur in RAM causing fewer physical writes to disk * ? 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. * There is a notion of a waypoint in number of logs.? The waypoint indicates all changed database pages caused by that number of the most recent logs are kept in memory.? These pages are not flushed until they the log that caused the change is outside the waypoint range.? The result is that the database always lags the committed transactions in logs.? This means that should you crash and lose a log in the waypoint range you can recover without a restore. * ? 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. * *Speak to checkpoint depth 32GB cost prohibitive due to 4GB DIMMs 64 bit allows addressing “infinite” amount of physical memory. So an Exchange 12 mailbox server can be provided plenty of RAM to use for its database buffer cache. With Exchange 2003, the limit is 900MB even with the 3GB switch (550 MB otherwise). With Exchange 12 there is no hard limit. We expect systems with 8 to 32 GB of buffer cache. The larger cache allows more database pages to be present in memory, thereby resulting in fewer disk IOs for reading. The larger cache has very little impact on the number of disk IOs for writing. Write IOs continue to be dominated by checkpoint advancement. * ? 2005 Microsoft Corporation. All rig