[
https://issues.apache.org/jira/browse/DERBY-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278824#comment-13278824
]
Rick Hillegas commented on DERBY-5691:
--------------------------------------
Hi Kim,
I'm a big fan of belaboring the obvious. Derby is used by a lot of people who
aren't database experts. What seems obvious to us may not seem obvious to many
of our users. Thanks.
> Document that Write Caching must be disabled to avoid possible database
> corruption
> ------------------------------------------------------------------------------------
>
> Key: DERBY-5691
> URL: https://issues.apache.org/jira/browse/DERBY-5691
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Environment: Microsoft Windows
> Reporter: Stan Bradbury
> Assignee: Kim Haase
> Labels: Write_caching
> Attachments: DERBY-5691-2.diff, DERBY-5691-2.stat, DERBY-5691-2.zip,
> DERBY-5691-3.diff, DERBY-5691-3.zip, DERBY-5691.diff, DERBY-5691.stat,
> DERBY-5691.zip
>
>
> Suggestion that we document a recommendation that Windows Write Caching be
> disabled on machines using Derby.
> The following article warns about Write Caching on Windows as a possbile
> source of database corruption:
> http://support.microsoft.com/kb/281672
> It is possible that this could be the cause of some unexplained Derby
> corruptions identified after power failure of other system interupt.
> Links explaining how to disable Write Caching:
> Win 2K: http://support.microsoft.com/kb/259716
> Win 2008: http://support.microsoft.com/kb/324805
> From the Windows 2008 article:
> With some third-party programs, disk write caching has to be turned on or
> off. Additionally, turning disk write caching on may increase operating
> system performance; however, it may also result in the loss of information if
> a power failure, equipment failure, or software failure occurs. This article
> describes how to turn disk write caching on or off.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
