THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

The Rambling DBA: Jonathan Kehayias

The random ramblings and rantings of frazzled SQL Server DBA

Diskeeper 2010 Update

A few weeks ago I blogged about A tale of CHECKDB failures caused by 3rd party file-system drivers that was related to a bug in the latest version of Diskeeper 2010.  I received an email from the company that they have released an update that resolves the problem.

http://www.diskeeper.com/blog/post/2009/12/28/New-Diskeeper-2010-update-%28140898%29.aspx

The fix was identified and blogged about on the Diskeeper blog within hours of my posting the original blog post:

http://www.diskeeper.com/blog/post/2009/12/10/IntelliWrite-and-SQL-DBCC-false-positives-Technical-Bulletin.aspx

Now the real question: am I going to turn the IntelliWrite feature back on in my servers?  I haven’t decided yet, but its not likely.  Its something that will be discussed with the server team since this product is installed by them and not by me, but they generally aren’t enthusiastic about enabling configurations that were previously problematic unless they are necessary, and I don’t think that this qualifies as necessary in our environment.

Published Tuesday, December 29, 2009 2:32 PM by Jonathan Kehayias

Comments

 

Carl Walden said:

What I suggest you do is not to automate the diskeep because by automating there is the possibility  you might corrupt the transaction logs I have experience such problems before so I run the diskeep manually by 2am every Saturdays. If you automated the diskeep it will also slow all users activities therefore all anti-virus and diskeep tasks are down manually.

December 30, 2009 11:23 AM
 

Amit said:

January 9, 2010 10:51 AM
Anonymous comments are disabled

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement