|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Yesterday @ 6:18 AM
Points: 768,
Visits: 194
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 12:22 PM
Points: 205,
Visits: 540
|
|
How about the restore functions?
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Yesterday @ 6:18 AM
Points: 768,
Visits: 194
|
|
Just like the backups, you can use the wizard or script. The restores worked fine. The coolest feature was the ability to restore all log backups in a folder with one command.
Aunt Kathi Microsoft (Former SQL Server MVP)
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 12:22 PM
Points: 205,
Visits: 540
|
|
"Restore all log backups in a folder within one command" is really useful in real world, esp. when you have to do the "recovery to the point". I once implemented this function through a complex t-sql SP before, maybe I should share with people here about how I implement this just to save a few $'s to purchase the off-shelf package.
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Yesterday @ 6:18 AM
Points: 768,
Visits: 194
|
|
I am using log shipping to replicate one database. When log shipping breaks, I have a VBScript that creates my log restore script for me to get it caught up again.
Aunt Kathi Microsoft (Former SQL Server MVP)
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Yesterday @ 12:22 PM
Points: 205,
Visits: 540
|
|
Log shipping is fine, but more often than not, people do not have the budget to replicate a huge-sized db, which is not adding any economic value.
|
|
|
|