For SQL DBA's (only):
Diskeeper 2010 with IntelliWrite currently has an issue where Database Consistency Check (DBCC) commands report problems with the database (though no actual problems exist). I guess it could be described as a "false positive" or "false alarm".
The issue is specifically that IntelliWrite's timing in expanding a file changed what the consistency check was expecting. Thereby DBCC incorrectly reports consistency errors. Turning off IntelliWrite makes the alerts go away. Then running DBCC confirms that no errors actually occurred.
So while the issue is very minor (no actual problem) major "problem indicators" do get set off, making for a potentially very unpleasant experience for a DBA. Something we apologize for.
On a positive note, we've repro'ed the issue and already have a fix. We're starting a field test tomorrow (on Friday, Dec. 10th). The fix should be broadly available later next week or early the following week (depending on how quickly the field test completes). If anyone is interested in testing this patch, you can contact Diskeeper at [email protected].
Until the fix is available, disabling IntelliWrite on a SQL database volume corrects the false alarms.
Lastly, I do want to add that this is the only common reported issue we have seen with IntelliWrite – it is an extremely stable and reliable technology. The software update that will come only needs to fix the issue discussed in this post.