I'd say if the client can give me the expected code errors, user errors, number of time someone will delete/drop/truncate a table, expected number of ora 600/7445 errors, I can pretty much give a estimate of db support time. Oh ... and did I mention failed backups, space shortage, SA availability, imports/exports etc?
Couple of days ago we spent about 5 hours relocating some tables from one data file to another ONLINE because system couldn't be taken down, the expected time was couple of hours, lest we knew that couple of tables had CLOBS, and a small procedure was dependent on that table. This procedure is used by EVERY piece of code in the database, so imagine what a nightmare it was for us. This is even when we were doing on-line moving on a 9012 db. HTH Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art!
*********************************************************************2 This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you. *********************************************************************2
