Re: Opinions for this storage parameters.

In article <E2F6A70FE45242488C865C3BC1245DA702505E97_at_lnewton.leeds.lfs.co.uk>, Norman says...
>
>Morning Richard,
>
>you wrote :
>
>>> Now, EVERY object that lives in the tablespace has EXACTLY the same
 sized
>>> extents.
>
>True, but then some silly b*gg*r goes and exports a table (or all of
>them) using the default COMPRESS=Y, drops them from the above tablespace
>and re-imports them. Not to get any perceived performance benefits of
>having all data in one extent (I know there are none !) but just because
>they wanted to. Now, your nicely set up tablespace has gone to hell and
>back.
>
>The number of problems I'v had with this sort of thing, and being sent
>exports of databases where this has gone on has caused me no end of
>problems.
>
>I love LMT with uniform sizes - what an absolute relief.
>
>Cheers,
>Norman.
>
>PS. I'm just having a bit of a rant because I've hit the above problem
>and the bleeding import won't work because the constraints are being
>created with stupid values which exceed the available space in the
>tablespace etc etc.
>:o(
>
>
>-------------------------------------
>Norman Dunbar
>Database/Unix administrator
>Lynx Financial Systems Ltd.
>mailto:Norman.Dunbar_at_LFS.co.uk
>Tel: 0113 289 6265
>Fax: 0113 289 3146
>URL: http://www.Lynx-FS.com
>-------------------------------------
>

Sounds like you've got a DBA at the other end there who believes that you need to take the defaults (why COMPRESS=Y is the default is just beyond me, but it is). Ask them if DBA stands for Do Bugger All? ;)

HTH. Additions and corrections welcome.

Pete

SELECT standard_disclaimer, witty_remark FROM company_requirements; Received on Wed Jul 03 2002 - 17:41:39 CEST