Originally posted by sreddy
I'm missing something here how does it matter to application what kinda B&R methodology you use for database. If I'm managing the database, I'm responsible for data on database not my manager. I will take the best solution for B&R not what manager wants cuz, he is favorite of Exp/Imp. Unless they do not want to give me hard disk to save my backup files (In that case I will not be having disk for exp dumps either).

This is not for the sake of argument but, for the sake of dba who needs take best measures for safe guarding the data on the database he is responsible for.
I wish it was that easy!

In my company (300,000+) the application is responsible for letting us know what is acceptable. some of the less critical apps can afford to loose 24 hours worth of data, so a daily export is fine for them. No need for Archive mode either.

Budget, licensces, certification and DASD come into play as well.
You have to have the proper liscence in place.
The app needs to be approved by upper management (tested, payed for, ect....
You need to plan ahead for the proper DASD and that costs money.
The impact your B&R methodology will have on the application. I know when we implemented archive log on one app, they called us screaming with performance problems.

So, around here you have to go through all the proper channels, you can't simply do what you want. Multiple departments have to get involved, and that has it's good and bad points.

MH