January 14, 2010 at 2:48 pm
So I have heard from many DBAs that taking a backup of a db helps the performance of the db in many ways and not just updating statistics, rebuilding indexes and other maintenance tools. It seems that there is something done in the background during a backup that helps the performance of the db. I am looking to find out what goes on behind the scenes that has this effect on the db (if there actually is any mysterious performance tuning going on). My objective is that I have an archive db that will be going to read only and actually only needs to have a backup done manually once a year but if there is something else that the back up does that would hinder the performance of this db if not done on a more frequent basis, then I would like the ability to run this performance tuning without the need of taking a backup. Any suggestions would be helpful for me researching or for those more experienced just tell me not to listen to everything that someone tells me.
Thanks
January 14, 2010 at 2:53 pm
backing up a database has no effect on performance. If you don't need frequent backups don't waste resources backing it up.
Just make sure you have got one you can restore from.
---------------------------------------------------------------------
January 14, 2010 at 6:26 pm
Perhaps you heard such a thing because some people schedule other tasks along with their backups. They are separate actions, and I prefer to schedule them separately since they usually have different scheduling needs.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply