Compress Log Shipping Options?
-
New here and this is my 1st post - so be easy on me.
First and foremost, I'm not a DBA so be especially easy on me!!Just setup 2005 log shipping on a previous 9.5GB database. After turning log recovery mode from simple to full, the DB size shot up to almost 12GB. (With simple, the transaction log was 2.5GB - after it remained at 2.5GB). It appears the DB has auto-increased in size due to the change to full. Not entirely sure why.. can someone explain this?
Also, it appears that when SQL is backing up the T-log (every 15 min) it can be quite large (30+ MB). This same 30MB file compress is a mere 5.5MB. These files are shipping over the WAN through a VPN tunnel that does not have unlimited bandwidth... Is there a way to compress these log files prior to sending them? I would prefer to avoid a scripting solution and would like to know if there is something inherant in SQL server or if there is a low cost add-on that would acheive this..
Thanks in advance for you help & time!
-
You'll have to do some scripting, but you can zip the log file after the backup and unzip it after copying it to the standby server. There are lots of cheap or free zip programs that can be called from the command line.
The data file does not auto-grow because you change the recovery model. It auto-grows because it needs more space. What are your auto-growth proeprties set at? How much free space is in the data file?
My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply