Re: JDEdwards and Uniform tablespaces

Jay-

Is there any way you can figure out from their scripts, etc. which objects do not get used? You could always place those in a sort of "dummy" tablespace, or group of tablespaces, with particularly small extents and just let them sit there.

Or, you might do a trial install with small-extent tablespaces and then run the product and identify the useless objects, then reinstall. Probably a tedious hassle, but may save lots of grief in the long run.

• ricky

Jay Strauss wrote:

> Hi,
>
> We're doing a JDEdwards implementation. I'm building a new database so I
> figure what better time to try out locally managed tablespaces and uniform
> extents. But when you install jdedwards it builds ~2200 tables, not all are
> used (20-25%), they build all the tables for all their modules, even if you
> don't use all the modules.
>
> Am I right in thinking - If I use uniform extents, when I build the tables,
> even the unused tables will have a least 1 extent allocated? Which
> depending on my extent size, could mean a lot of wasted space.
>
> - Is there anyway to build a table an not allocate the first extent?
> - If during table creation, I specify the extent size, does that override
> the uniform extent size? (I doubt it).
> - Am I better off just using a default storage spec of:
> initial 1k
> next 50M
> pctincrease 0
>
> Thanks
> Jay
>
> --
> Jay Strauss
> jjstrauss_at_yahoo.com
Received on Tue Apr 10 2001 - 14:07:52 CDT