RE: Database Setup

Posted in 2000

Topics: Performance & Tuning, Storage & Space Management, SQL Development & Query Writing, Triggers, Constraints & Referential Integrity, Migration, Import/Export & Data Conversion

Raj Muralidharan — Tue, 5 Sep 2000 11:56:48 -0500 — source: Informix-list mailing list archive (1991-1998)

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0175A.47E920D0 Content-Type: text/plain; charset="ISO-8859-1" You can't do this to system catalogs. That said, there is a new feature coming in 9.3 that will allow the system catalogs to be re-organized using oncheck. Raj -----Original Message----- From: Sergey Turin [mailto:sturin@mow-co.ru.dhl.com] Sent: Monday, September 04, 2000 4:49 AM To: informix-list@iiug.org Subject: Re: Database Setup Using "ALTER NEXT SIZE xxx" it's possible to have 1-2 extents for system tables ( sysprocbody, sysprocplan, systriggers etc). It might be very little positive performance impact, but "oncheck -pe" output would be readable. Sally Woolrich <sally.woolrich@comino.com> wrote in message news:39af7001.234407780@comino-leeds... > > > Except that as you load the table adjacent extents will 'join up' to > become one. We loaded a much larger db via dbimport and when it was > finished (before they started using it) the only tables with more than > 1 extent were system tables, and it's unavoidable for those tables. > ------_=_NextPart_001_01C0175A.47E920D0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3DISO-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2652.35"> <TITLE>RE: Database Setup</TITLE> </HEAD> <BODY> You can't do this to system catalogs.  That = said, there is a new feature coming in 9.3 that will allow the system = catalogs to be re-organized using oncheck.  Raj -----Original Message----- From: Sergey Turin [<A = HREF=3D"mailto:sturin@mow-co.ru.dhl.com">mailto:sturin@mow-co.ru.dhl.com= </A>] Sent: Monday, September 04, 2000 4:49 AM To: informix-list@iiug.org Subject: Re: Database Setup Using "ALTER NEXT SIZE  xxx" it's = possible to have 1-2 extents for system tables ( sysprocbody, sysprocplan, systriggers etc). It = might be very little positive performance impact, but "oncheck -pe" output would be = readable. Sally Woolrich <sally.woolrich@comino.com> = wrote in message <A HREF=3D"news:39af7001.234407780@comino-leeds" = TARGET=3D"_blank">news:39af7001.234407780@comino-leeds</A>... > > > Except that as you load the table adjacent = extents will 'join up' to > become one.  We loaded a much larger db = via dbimport and when it was > finished (before they started using it) the = only tables with more than > 1 extent were system tables, and it's = unavoidable for those tables. > </BODY> </HTML> ------_=_NextPart_001_01C0175A.47E920D0--

Related threads

Glossary

dbexport / dbimport