If you limit the max file size, don't you have the same situation as when you don't enable "set & forget"? But then, when the disk/LUN/etc fills up you'll still have to swing into action..
An adequate DBA monitors tablespace usage, so the answer to the question would be "in DBA salaries"... ;)
Auto-extend is just a feel-good marketing tool, imho. Cheers, Tony On 14/03/10 10:50 AM, Michael Dinh wrote:
Even with autoextend, you can control the max file size. The question is, how do you measure the cost of a failing process because of inadequate storage? -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Joe Smith Sent: Sat 3/13/2010 11:38 AM To: oracle-l@xxxxxxxxxxxxx Subject: cost of autoextend How do you measure the cost of a datafile autoextending? thanks. _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/210850553/direct/01/
-- //www.freelists.org/webpage/oracle-l
