Re: Stripe and Mirror Everything?

On Thu, 16 Sep 2004 12:51:14 -0400, David E. Grove wrote: It'll reduce the IO overhead, but archives will still copy all those pages that were written and rewritten to the tapes. TEMPDB spaces are not archived! Art S. Kagel > "Claus Samuelsen" <csa@eye-bee-em.com> wrote in message > news:41494202$0$212$14726298@news.sunsite.dk... >> >> I would certainly consider two dbspaces - the root dbspace and a temporary >> dbspace. In a logged database transaction record writing (which is >> typically the most io intensive in an oltp system) can be reduced by having >> the temporary tables in a non-logged dbspace. There's also a minor benfit >> in that temporary dbspaces is not backed up. >> >> > I hadn't thought of that. Would using "WITH NO LOG" clause also be a way to > eliminate that overhead? I guess that would only work for explicit tables, > huh? > > DG

Thank you. Good point. I am now using two dbspaces: rootdbs and tempdbs. "Art S. Kagel" <kagel@bloomberg.net> wrote in message news:pan.2004.09.21.16.06.23.610288.1355@bloomberg.net... > On Thu, 16 Sep 2004 12:51:14 -0400, David E. Grove wrote: > > It'll reduce the IO overhead, but archives will still copy all those pages > that were written and rewritten to the tapes. TEMPDB spaces are not > archived! > > Art S. Kagel > > > "Claus Samuelsen" <csa@eye-bee-em.com> wrote in message > > news:41494202$0$212$14726298@news.sunsite.dk... > >> > >> I would certainly consider two dbspaces - the root dbspace and a temporary > >> dbspace. In a logged database transaction record writing (which is > >> typically the most io intensive in an oltp system) can be reduced by having > >> the temporary tables in a non-logged dbspace. There's also a minor benfit > >> in that temporary dbspaces is not backed up. > >> > >> > > I hadn't thought of that. Would using "WITH NO LOG" clause also be a way to > > eliminate that overhead? I guess that would only work for explicit tables, > > huh? > > > > DG