On 8/2/07, Orlando Andico <[EMAIL PROTECTED]> wrote: > I must add... > > Using "export" with Oracle WILL WORK. No doubt that's why you claim > that this is what you do on live databases and get away with it. But > it's horribly sub-optimal and will only work if your transactional > volume is not high. > > But if you are running say 20,000 continuous transactions per second, > the instant you press "Enter" to start your "export" --- goodbye SLA. > There are many far better ways of backing up a live Oracle database > than "export" :O That's got to be the worst way to do it.
No doubt, there are many ways to skin a cat. My example being the simplest and most straight forward. Nice of you to point out it's absurdity when set against 20,000 continuous transactions per second. Sure there can be some other solution right? Like some sort of database replication or load balancing a dabatase cluster so that it doesn't get hit at 20,000 per second? Backing up off the another server's replicated data? Or having stored procedures which make copies of data as it is being stored? We can go on and on. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
