SQL Performance (MOSC)

MOSC Banner

performance of large delete from large tables

edited Jan 16, 2020 2:50PM in SQL Performance (MOSC) 13 commentsAnswered

Hi,

Trying to improve the performance of a large delete from a number of related tables linked via cascade delete constraints and wondering what could be used to improve the performance of the operation.

Would it possibly run faster if the child table data was deleted first and then delete the parent data afterwards?

Would there be a benefit to trying to put some of the tables in memory, perhaps using the db_big_table_cache_percent_target parameter?

Here is the exection plan when running the query:

There are 3 tables in the configuration

CUSTOMERS

TRANSACTIONS

DATA_ELEMENTS

The delete statement is:

Tagged:

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