non existent tables might be getting written to a file

if the dump causes a 0 byte file to be written then we probably don't want to zip it, but instead get rid of it and notify the user or something?

This should make sure everything works correctly if numbers are skipped also, so if you had:

001...
003...

That it would still run them correctly (001 then 003) and still run them all without getting mad there isn't a 002...
