Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL 2005 vs. SQL 2008 Part 1 - (Backup File Sizes & Times)


SQL 2005 vs. SQL 2008 Part 1 - (Backup File Sizes & Times)

Author
Message
Kevin-458339
Kevin-458339
Old Hand
Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)

Group: General Forum Members
Points: 359 Visits: 3173
Comments posted to this topic are about the item SQL 2005 vs. SQL 2008 Part 1 - (Backup File Sizes & Times)
Anipaul
Anipaul
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6473 Visits: 1407
The speed of the backup is a good news. But I have couple of questions? Will it take less space in the tape drive due to compression? Will it be a reliable backup?

Smile



Kevin-458339
Kevin-458339
Old Hand
Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)

Group: General Forum Members
Points: 359 Visits: 3173
Hi

On your 2 questions:

1) Space on Tape: if your tape device does compression on the fly as ours does. Our usual space saving is approx 65% when going onto tape.

This means that the 3.5GB file is stored on tape as 1.2GB - this is about 200MB more than the SQL 2008 Compressed backup.

If the original 3.5GB file is zipped using maximum compression then the ZIP file is approx 820MB (note: this maximum compression takes longer than the SQL 2008 Compression Backup)

So, this means that there is potentially 200MB that could be saved when storing onto tape for this 3.5GB database backup.

2) Reliability: because the SQL engine is doing the compression and not a third-party vendor, I am reasonably confident that this backup should be seen as reliable as the original .BAK without compression.

Thanks
Kevin
Mª del Prado Barba
Mª del Prado Barba
SSC Rookie
SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)

Group: General Forum Members
Points: 47 Visits: 95
Hi,

and what about to restore? Do you need more additional space on disk to uncompress first?

Thanks in advance,

Prado
Kevin-458339
Kevin-458339
Old Hand
Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)

Group: General Forum Members
Points: 359 Visits: 3173
Hi

The "uncompress" actually happens inside the SQL Engine - so no additional space is required for a "temp" file. The only space required is the size of the Database and Transaction Log.

Note: If a backup file is 900MB - the actual size of the database Data file is 3.5GB and the Log 100MB - then this is the amount of space required on disk for the restored Database files (Data and Log)

Thanks
Kevin
SuperDBA-207096
SuperDBA-207096
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1563 Visits: 711
Nice work Kevin!

The compress backups feature will come in handy in many environments - certainly will save space.

One question - I didn't see metrics for restoring. I'd be interested in seeing what the differentce in restore time would be for a compressed backup vs. non-compressed.

The reduced backup time was an interesting effect, it shows that the disk is probably the limiting factor in this instance.

Mark
Anipaul
Anipaul
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6473 Visits: 1407
Kevin (5/5/2008)
Hi

On your 2 questions:

1) Space on Tape: if your tape device does compression on the fly as ours does. Our usual space saving is approx 65% when going onto tape.

This means that the 3.5GB file is stored on tape as 1.2GB - this is about 200MB more than the SQL 2008 Compressed backup.

If the original 3.5GB file is zipped using maximum compression then the ZIP file is approx 820MB (note: this maximum compression takes longer than the SQL 2008 Compression Backup)

So, this means that there is potentially 200MB that could be saved when storing onto tape for this 3.5GB database backup.

2) Reliability: because the SQL engine is doing the compression and not a third-party vendor, I am reasonably confident that this backup should be seen as reliable as the original .BAK without compression.

Thanks
Kevin



Thanks Kevin on your prompt reply. This clears my doubt. Smile



Kevin-458339
Kevin-458339
Old Hand
Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)Old Hand (359 reputation)

Group: General Forum Members
Points: 359 Visits: 3173
Yes, the restore from compressed .BAK file will be an interesting item to investigate.

I will get my environment up and running and either post feedback on this discussion or provide feedback in the form of a more in-depth technical article on the topic of Restore & Backups with SQL 2008.

Thanks
Kevin
Mª del Prado Barba
Mª del Prado Barba
SSC Rookie
SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)

Group: General Forum Members
Points: 47 Visits: 95
Hi again,

A lot of thanks for your answer. Your explanations are very useful so we'll wait your feedback about the test for restore.

Thanks,

Prado
ALZDBA
ALZDBA
SSCertifiable
SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)

Group: General Forum Members
Points: 7949 Visits: 8845
Thank you for highlighting this valuable feature.
Saving +60% is certainly worth investigating it to the bone, considering the vase amount of backup data we produce.

Nowadays we compress the backup by using disk compression at our safezone. (backups are procuded local and xcopied to safezone)

Won't compression on compression produce an overhead ?

Johan


Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere w00t

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


press F1 for solution, press shift+F1 for urgent solution :-D


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me Alien but most of the time this is me Hehe
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search