If you have some other reason to commit the changes to the first table (e.g. triggers) then just know they fire when the DML is executed, but not committed until the commit. A single transaction is treated as a single unit of work.

So, unless there's something weird going on, then what Drew said is exactly correct. If you have a RECONFIGURE, it can't be inside a transaction. A BACKUP can't be rolled back and have the file be deleted from disk. Other than this type of thing, you should be good. Test it out as a single transaction and see if the whole thing works.