After looking and finding the close answer, I'd like to post a follow-up, but separate, question to this one (split db to fit on ssds)
I have a 60 gig database that is growing quickly, due to one table that holds scanned documents. We are pushing to move old paper to scanned docs, and I have no choice that this is how we handle saving scanned documents. I was thinking about adding a new file group, and move that table to the new FG by recreating the unique clustered index for that table to the new FG.
I did that on a test box and surprisingly, the OS file size of the original MDF did not significantly change, nor did the new secondary FG size up to the corresponding ratio of that one table's size to all the tables.
I was thinking the OS file sizes should change on the order of the size of the table that was moved. What am I missing?