October 13, 2010 at 7:31 am
hello experts,
i have taken a backup of database, backup size around 112 gb, when i archived it as a .RAR file it reduced upto 5.5 GB only, how did it happen, i have a doubt tht is archived correctly or not? if it is archived correctly how can it reduced upto that much level??
October 13, 2010 at 7:33 am
Did you do a compressed back up or a normal back up?
-Roy
October 13, 2010 at 7:36 am
i have done a normal backup
October 13, 2010 at 7:54 am
Take a compressed backup. It will almost be the same size as that of the .RAR file. When you take a normal back up, the data is not compressed. The RAR compression and SQL compression will be able to compress this. Also depending on the data you have in your database, compression ratio might change. For instance string data will get more compression than ints (As far as I know).
-Roy
October 13, 2010 at 7:58 am
i cant take compressed backup, using 2005.
October 13, 2010 at 8:09 am
I thought you were using SQL 2008 since the question is in the SQL 2008 forum. The normal back ups does not compress the data. Therefore RAR file can compress it. If you want to see if the file that got compressed is still valid, do a restore of the header and see if it is good.
-Roy
October 13, 2010 at 8:09 am
sachinsoni84 (10/13/2010)
i have taken a backup of database, backup size around 112 gb, when i archived it as a .RAR file it reduced upto 5.5 GB only, how did it happen, i have a doubt tht is archived correctly or not? if it is archived correctly how can it reduced upto that much level??
Uncompressed database data tends to compress very well - there's usually a lot of blank space and repeated values, for example.
You should always verify your backups, ideally by uncompressing them and restoring them to a second server, and then checking the contents.
October 13, 2010 at 8:50 am
ohh i placed question in 2008 forum, sorry
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply