Originally posted by sreddy
Mr. Hanky,

Thats whole another story of enabling archive mode and issues with performance which can be tuned for optimum performance. I don't see benifits having only exp/imp B&R methodology. I see only the practical benefit off of exp/imp methodology is object level recovery (Human mistakes of table drops etc.) Anyway, it has become more likedebate now
HA! Not in an NT envioronment with limited resources and disk space. One batch job and you come in to a hung database. It quickly became a maintenence nightmare. Again, the apps group and another group (that handles the instance) decided on this and it was implemented. I was the one that insisted on removing it.

I really do not want to get into a imp/exp B&R debate because it is a moot point. We all know it is not the best B&R methodology, BUT in the real world it does exist. I inherited it, and as I said it is for less critical apps. I don't think we could afford to have everyone of our apps running in archive log mode with multiple backups, ect...

MH