I need to delete several clients from our shared database. I will be disabling the website tonight in order to do this. It takes about an hour to delete a client but if I change the recovery mode of the database to simple first then it takes half the time. But If I do that and then change it back to full after then the transaction logs are out of sync and useless right? Suggestions?
You have to run a full or diff backup to startup the tlog chain again after you switch back to FULL.
I don't understand why changing the recovery model speeds up performance. That doesn't make any sense. There must be something else going on here, such as severe IO issues.
quote:I don't understand why changing the recovery model speeds up performance. That doesn't make any sense. There must be something else going on here, such as severe IO issues.
It is deleting about 18 million records so I guess not having to commit to the tlogs means it is faster.
quote:I don't understand why changing the recovery model speeds up performance. That doesn't make any sense. There must be something else going on here, such as severe IO issues.
It is deleting about 18 million records so I guess not having to commit to the tlogs means it is faster.
Nope. Transaction log is used regardless of recovery model. You've got something else happening here. Maybe autogrow problems and not often enough tlog backups?
implications of temporarily changing DB mode?
Posted - 06/01/2012 : 11:59:54
