db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-381) Doc review: Derby Server and Admin Guide
Date Tue, 28 Jun 2005 18:43:01 GMT
    [ http://issues.apache.org/jira/browse/DERBY-381?page=comments#action_12314633 ] 

Mike Matrigali commented on DERBY-381:
--------------------------------------

The reclaiming unused space section of the server guide should be updated to also mention
the new space reclamation routine being provided in this release - SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE.
 Documentation on how to call this is already in the reference manual.  I would recommend
something like the following:

If you determine that a table and its indexes have a significant amount of unused space, use
either the SYSCS_UTIL.SYSCS_COMPRESS_TABLE or  SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE to
reclaim that space.
SYSCS_COMPRESS_TABLE is guaranteed to recover the maximum amount of free space, at the cost
of temporarily 
creating new tables and indexes before the statement in committed.  SYSCS_INPLACE_COMPRESS
attempts to reclaim
space within the same table, but cannot guarantee it will recover all available space.  The
main difference is that SYSCS_INPLACE_COMPRESS uses no temporary files and moves rows around
within the same conglomerate.

SYSCS_COMPRESS_TABLE - guarantees all free space returned, will use temporary space until
transaction is committed.
SYSCS_INPLACE_COMRESS- likely to use more cpu, likely to return less space, but will not use
any temporary space.



> Doc review: Derby Server and Admin Guide
> ----------------------------------------
>
>          Key: DERBY-381
>          URL: http://issues.apache.org/jira/browse/DERBY-381
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For: 10.1.1.0

>
> This issue tracks comments for the Derby Server and Administration Guide. The deadline
for posting comments is Tuesday, June 28, noon Pacific time.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message