I had a series of SQL Server errorlog (1 to 6) files taking up 39GB. I needed the space for database growth. Being a belt and braces sort of guy, I zipped them (or moved them to compressed folder) first. This reduced the 39GB to 1GB. I therefore expected to see my disk free space increase by 38GB. But no! Stayed exactly the same.
I tried restoring them back, but this didn't complete as there was only the original 10GB free and not enough space for an extra 38GB. I recycled the logs 6 times using sp_cycle_errorlog in case SQL had somehow kept hold of them. This reduced the size to a handful of KB as expected, but still made no difference to the disk free space.
Never seen anything like this before. Anyone any ideas?
SQL 2012, Windows 2012, hosted on VMWare.
