I recently was asked to ship a .bak file of our database to a client, and through reindexing all tables with a 100% fill factor (to make sure there were no empty slots), and resizing the transaction log, and 'shrinking' the file was still large (before 7zipping).
I can't find the information about what happens to index data during a .bak anywhere. So, the question is, does a .bak file exclude the index data already? or is there a way of stripping out all index data before taking a .bak and just rebuilding it on restore?
I did try looking for similar posts before posting, apologies if this has already been asked/answered.
Are there a known set of steps to make the smallest restorable .bak file when you
a) don't care about transcations (you're in single user mode, all transactions are committed).
b) don't care about indexes/statistics which can be rebuilt
c) don't care how long it takes to restore.