Comments
Sort by recent activity
Hey!
Yikes! :oops: OK, I dont know how I didnt notice that there was a compression level of 0! :oops:
I did try all of the compression levels besides 0, and they were all larger.
Thanks! / comments
Hey!
Yikes! :oops: OK, I dont know how I didnt notice that there was a compression level of 0! :oops:
I did try all of the compression levels besides 0, and they were all larger.
Thanks!
petey wrote:
The next version of SQL Backup will do this.
So, when is this next version of SQL Backup due to be released :?:
Thanks :!: / comments
petey wrote:
The next version of SQL Backup will do this.
So, when is this next version of SQL Backup due to be released :?:
Thanks :!:
MrDave wrote:
What type of error are you getting because I have had it fail and leave the logs even with the move to?
It was failing due to out of sequence log files.
When setting up log shipping, I accidentally moved the first log file when I moved the full backup, and when I attempted to run a wildcard *.* restore, it moved ALL of the log files that matched the restore criteria... this could have made it time consuming to figure out which log file was the last file restored had log shipping not just been set up.
Thanks for the information petey :!: / comments
MrDave wrote:
What type of error are you getting because I have had it fail and leave the logs even with the move to?
It was failing due to out of sequence log files.
When setting up log shipp...