sql server - Optimized Way of Scheduling a Differential Backup -


i working data warehouse sql server 2012 , wondering optimized, automated procedure backup/restore strategy.

current observations , limitations:

1) cannot use transaction logs affect load performance - datasets potentially huge large transactions

2) current plan full backup every week , differential backup every day

i not sure when dml operations happen depends on application's usage, there way track number of changes database trigger differential backup? way not affect performance? not want taking unnecessary differential backups.

would change tracking solution scenario? or there overhead involved? not need know actual data changed, fact changed amount.

thanks in advance!

well, there's ( http://www.sqlskills.com/blogs/paul/new-script-how-much-of-the-database-has-changed-since-the-last-full-backup/ ). i'm trying figure out problem you're trying solve. is, if find size below threshold, (by definition) cheap do.


Comments

Popular posts from this blog

javascript - Jquery show_hide, what to add in order to make the page scroll to the bottom of the hidden field once button is clicked -

javascript - Highcharts multi-color line -

javascript - Enter key does not work in search box -