You can’t Delete a Single Table by editing a SQL Server backup file. I keep the original backup intact.

Restore into a separate staging database if a new backup must exclude a table. Review dependencies before removing it there. Then create and test a new backup. Don’t drop a production table to reduce backup size.
For storage size, assess backup compression on the supported edition and release. It can reduce space and I/O. It doesn’t remove tables, erase sensitive data or guarantee a ratio. Compression isn’t universally enabled by default.
I heard this question during an interview. Changing a database and changing an existing backup are different operations. The existing backup remains a record of the database when it was taken.
A new backup without one table doesn’t erase older copies. Copied media, snapshots and restore chains can retain that data. Treat retention and data removal as separate policies.
Related reading
- Configure the Backup Compression Default Server Configuration Option
- How to Enable Backup Compression On by Default
- SQL SERVER – Playing with Backups and Compression
- Effect of Compressed Backup Setting at Server Level on Database Backup
A backup file is not an editable table container, it is a recovery artifact.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
Discover more from SQL Authority with Pinal Dave
Subscribe to get the latest posts sent to your email.





4 Comments. Leave new
Oracle gives option to take backup without data (schema only), is there any way to do so in sql server?
You can export the table schema without data. There is an option for that in SQL server
Another way is restore db as a new from the backup, delete table and backup the new db )))
I got surprised , is it actually possible to delete a table from bak file .. after reading this . i just thanked god .. it should not happen even ..:)