SQL Performance (MOSC)

MOSC Banner

Locking stats at 0 rows on table improves performance

edited Aug 16, 2016 5:01AM in SQL Performance (MOSC) 5 commentsAnswered

Hi All,

     We have a table(JOBDATA) for which data is populated dynamically as part of application(J2EE + JDBC) execution. Table is always present in DB, however rows are populated at the start of the job run and deleted after the job completes. The no.of rows in table keeps varying depending on the Job Run. If we gather stats on the table before process run it is considering 0 rows and performance is decreasing significantly. As job run in a nightly batch we cannot gather stats on the table when the table is completely populated.

However we have observed that truncating the table and gathering, locking stats has improved the performance of the job. I want to understand why this is improving the performance. Is there any better way to do this?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center