I was just reading this article where the author talks about the file system fragmentation that can be caused by growing database files. There was one bit that I didn't quite follow.
What about Windows defragmentation tools?
Although you can use a Windows defragmentation tool to defragment your database files, these tools simply move chunks of files around to get them contiguous. This moving of chunks of files can cause internal fragmentation that you might not be able to resolve easily.
Is the author saying here that the disc defragmenter makes no attempt to put the chunks of files in the correct sequence or have I misunderstood? If he is saying that then is this a limitation of all disc defragmenter utilities - even commercial ones?
Any external fragmentation tool (doesn't matter commercial or free) does not restructure the internal contents of the file, unlike DBCC REINDEX.
After defragmentation, the defragmented file will be a bit for bit duplicate of the original. Therefore, any holes within the database are still present and you will still need, from time to time, to rebuild your indexes to combat internal fragmentation.
Not everyone has a spare filegroup.
[cynical]
Seems to me a pitch to use "Kronos Workforce" as a magic way to do stuff your DBAs should be doing anyway. I've had the same issues with vendors pitching some whizzy (expensive) product to my management to do standard DBA tasks
[/cynical]
Edit: It appears I've misunderstood. Kronos is not a DBA tool.
However, the FUD in the article could be explained by these "tweaks"