November 23, 2005 at 11:56 am
Is there a way to determine the size of a full DB backup?.
We're trying to determine a if is there a rule of thumb for the space needed for a full, SQL native backup.
Thank you
November 24, 2005 at 1:14 pm
At least, it will occupy the space already used of the DB. You can see this on Enterprise Manager or sp_spaceused.
November 28, 2005 at 4:27 am
In our environment, we observed that it was doing approx a 20-30% compression. So a 10 GB database was creating a 7-8 GB backup file.
As a sidenote, we just implemented Red Gate's SQL Backup & we are now getting 70-95% compression rate. We are saving a lot of disk space using this. It is working very well for us.
HTH,
John
November 28, 2005 at 8:11 am
I'd say that the native backup compression depends upon the amount of free space in the data pages (fill factor related), it seems sensible that SQL wouldn't want to back up free space and this includes the space not used in the pages.
I'm in the middle of trialing SQL Backup and Litespeed, both seem to work really well compression wise so i guess our decision is ultimately going to be made on price rather than anything else.
November 28, 2005 at 3:15 pm
I've used 'native'/'free' compression utilities that aer separate from the SQL BACKUP at varying times ... I've seen the space savings vary between 30-70% ... quite a wide swing ... it all depends on the page fullness and amount of NULL things in the database ... so for estimating purposes I'd say you should always be able to get at lease 30% savings ... anything else is a 'bonus'.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply