![]() What should i do after i move the compressed backup files to destination server? Do i have to uncompress the backup files or can i restore directly with that files? Thanks a lot for everyone.My database is almost 1TB and i want to compress it 80-90 % so i can move easily to other location.Which tool will be best for this scenerio? Please advise. You might want to take a look at all 3 products.-ec I would contact quest for a quote.other similar products are SQL Backup from red-gate software and idera SQL Safe. we have used it for years and have come to depend upon it. ![]() Installation is easy as well.As mcrowley said, the only think is a spike in CPU when backing up.EDIT: Pricing (AFAIK) was per processor, but that was when it was owned by Imceda, take a look at Seems to work quickly and restores are good. Used it in a few places i've worked and never had any problems with it. So, if you are already using a lot of CPU, this may not be the tool for you. One thing to note is when the backup begins, the CPU will spike up. Our databases are largely text/image data, so we only get about 50% compression. It works well, and it restores well, too. We have used SQL Litespeed with SQL 2005 64-bit. How much does it cost?Please experts, Throw some light. How is compression ratio of backup files and how does it work with SQL server 2005? Is it easy to install in Production environment. We have 1 TB database and moving to different location so we want it to be done fast. We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with.
0 Comments
Leave a Reply. |