home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!uchinews!gsbacd.uchicago.edu!cs_mj
- From: cs_mj@gsbacd.uchicago.edu (Mark Jaeger)
- Subject: Re: Q: slooow access to FE catalogs (ABF,VIFRED)
- Message-ID: <1992Nov23.143400.1@gsbacd.uchicago.edu>
- Lines: 26
- Sender: news@uchinews.uchicago.edu (News System)
- Organization:
- References: <00963E7D.8D984880.30414@hal.hahnemann.edu>
- Date: Mon, 23 Nov 1992 20:34:00 GMT
-
- In article <00963E7D.8D984880.30414@hal.hahnemann.edu>, "Anthony J. Rzepela"
- <rzepela@hal.hahnemann.edu> writes:
-
- > Our development database is fairly heavily populated with applications,
- > frames, forms, and the like. To battle the EXTREMELY sluggish ABF startup,
- > I have run SYSMOD with the INGRES flag (which supposedly optimizes the
- > base product's catalogs for VIFRED, ABF, etc.), but still, ABF starts
- > up like a tortoise... Also, choosing 'RUN' from ABF took
- > so long just to compare the dates, I could not do it without going insane...
-
- It's just possible that you could get _some_ benefit out of doing
- "optimizedb" on the front end system catalogs. I don't remember the
- details, but you have to either specify the "-zc" switch, or name the
- tables explicitly with the "-r" switch, or both.
-
- You could also try running with the II_EMBED_SET environment variable
- set to "printqry" in order to capture the queries to a file, and then
- look at the performance statistics. That might give a clue which ABF
- queries are taking too long, and what could be done to speed them up.
-
- --Mark Jaeger internet: cs_mj@gsbvax.uchicago.edu
- Graduate School of Business yellnet: (312) 702-0328
- University of Chicago faxnet: (312) 702-0233
- Disclaimer: My opinions are my own and not those of my employer.
- Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
-
-