| sjgross 2002-12-17, 2:23 pm |
| Hi Naresh,
I'm not sure if this is what you are talking about but I found the following:
"Controller write caching can also speed up SQL Server I/O. The problem with this is that SQL Server will not know about the write caching, and will assume that when it writes a page to disk, that it was written successfully to disk. While this will be the case in most instances, it may not always be the case. If the server should fail before the data in the cache has been written to disk, then that data will be lost and your SQL Server databases may become corrupted.
While a battery backup for the cache can help reduce this problem, they introduce their own problems. For example, what if the server's motherboard fails and you need to move the drives to a new server. Will you be able to also move the cache controller to the new server, and will the data being backed up still be available in the new server? I personally never use write caching. The potential benefits don't outweigh the potential problems. To find out how to turn our I/O controller's write caching ability off and on, you will need to check your I/O controller's vendor. [6.5, 7.0, 2000]" from http://www.swynk.com/sqlhome/tips/mcgeheegensql4.asp
Also check out this knowledge base article from Microsoft:
http://support.microsoft.com/defaul...B;en-us;q230785 |