[
https://issues.apache.org/jira/browse/DERBY-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688535#action_12688535
]
Kathey Marsden commented on DERBY-3787:
---------------------------------------
Not a show stopper for the release, but in beginning my buddy testing,
I noticed the examples should use CALL e.g.
CALL SYSCS_UTIL.SYSCS_UPDATE_STATISTICS('SAMP','EMPLOYEE','PAY_DESC');
CALL SYSCS_UTIL.SYSCS_UPDATE_STATISTICS('SAMP', 'EMPLOYEE', null);
Also in the Tuning Guide under Working with Cardinality Statistics -> When
Cardinality Statistics Go Stale we should refer users to the
SYSCS_UTIL.SYSCS_UPDATE_STATISTICS stored procedure to update their statistics
and cross reference the reference guide.
Should I open up a new issue for these improvements or is it ok just to post
them here?
> Document the new system stored procedure SYSCS_UTIL.SYSCS_UPDATE_STATISTICS
> which was added as part of DERBY-269
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3787
> URL: https://issues.apache.org/jira/browse/DERBY-3787
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.5.0.0
> Reporter: Mamta A. Satoor
> Assignee: Laura Stewart
> Fix For: 10.5.0.0
>
> Attachments: DERBY-3787-2.diff, derby3787.diff,
> rrefupdatestatsproc.dita, rrefupdatestatsproc.html, rrefupdatestatsproc.html,
> rrefupdatestatsproc_2.html
>
>
> DERBY-269 added a new system stored procedure in Derby 10.5 to provide the
> users a way to update the statistics for all the indexes or one specific
> index on a table. We should document this in our documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
