Yes, fully aware of Paul's article, and "DON'T", et al...
This is SQL 2014 Enterprise - Build 12.0.5538 - SP2 CU3 - iron - 2x8 1TB RAM - all SSD.
There is an unused FILESTREAM data file:
file_id Size in MB type_desc state_desc is_percent_growth growth Growth in MB 65537 0 FILESTREAM ONLINE 0 0 0
A data migration by a.n.other Team inadvertently filled the entire data drive. Adding another set of RAID-10 disks to the existing volume would take two weeks (Hosting Vendor doesn't move very fast). As it is full, SQL Monitor is showing the space as full and alerting to that effect.
Aim: bring the data file down from 2.1TB to at least 20% less, to stop the nag-alert, as that's getting Support's attention, Hosting and internal, and we would like to stop those needless investigations.
So we can stop the SHRINKFILE if we need to, we nibble away in 5GB chunks. The file is at 2135040MB - still too high to shut the Alerts up. 106GB Free on the 2.18TB drive.
The target is 2129920MB for the current chunk.
The Shink ==> Files SSMS Dialog shows the minimum is 1391374MB - we went nuclear on garbage-collection and post-migration truncations.
2018-03-05 16:21:48.730 - Started: Original Size 2135040 MB 2018-03-05 16:21:48.730 - Shrink: to 2129920 MB File ID 1 of database ID 8 cannot be shrunk as it is either being shrunk by another process or is empty. DBCC execution completed. If DBCC printed error messages, contact your system administrator. 2018-03-05 16:22:11.250 - Ended: Shrink failed to run - see Messages
The is no such "...another process...", neither, obviously from SSMS Shrink's perspective, is it "...empty." In fact, this was run on as "silent" a box as we can get - just two DELAY pollers, and nothing, but nothing else running according to sp_whoisactive.
I tried adding some space and retrying. I had to add MANY MB, not just a few, as was suggested. The first 5GB SHRINKFILE went OK, then the above error.
Can anyone assist, please? (Seriously hope it's something obvious to a "real" DBA) With thanks.