Reminds me of when a customer's database kept crashing with an error code indicating the disk was full. Except Windows Explorer showed the disk having hundreds

Reminds me of when a customer's database kept crashing with an error code indicating the disk was full. Except Windows Explorer showed the disk having hundreds of gigs free... Took us a little while to figure out that the problem was the database file was so fragmented NTFS couldn't store more fragments for the file[1]. What had happened was they had been running the database in a VM with very low disk space for a long time, several times actually running out of space, before increasing the virtual disk and resizing the partition to match. Hence all the now-available disk space. Just copying the main database file and deleting the old solved it. [1]: https://superuser.com/questions/1315108/ntfs-limitations-max-fragments-per-file https://superuser.com/questions/1315108/ntfs-limitations-max...