OraFAQ Forum: Performance Tuning » Partitioning a table in Source

Home » RDBMS Server » Performance Tuning » Partitioning a table in Source (10g)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Partitioning a table in Source [message #326085]

Tue, 10 June 2008 02:43

beetel
Messages: 96
Registered: April 2007

Member

Hi,

We have an Oracle ERP as the source of our Datawarehouse. The tables are growing fast and we query the tables based on UPDATE_DATE -- which takes forever. If we make these tables as range-partitioned on UPDATE_DATE, is that wise?? The problem is that this column gets updated in the source (application) very often and I think partition keys should not be updated.

Please help Smile

Report message to a moderator

Re: Partitioning a table in Source [message #327528 is a reply to message #326085]

Mon, 16 June 2008 15:04

JackyShu
Messages: 25
Registered: May 2008

Junior Member

probably not a good idea if you need to update that column

Report message to a moderator

Re: Partitioning a table in Source [message #327570 is a reply to message #326085]

Mon, 16 June 2008 23:29

Michel Cadot
Messages: 68665
Registered: March 2007
Location: Nanterre, France, http://...

Senior Member
Account Moderator

Updating partition means moving the row from one partition to another one which is expensive: one delete + one insert in addition to your update + a more complex operation than usual on each index involving the partition column.

Regards
Michel

Report message to a moderator

Previous Topic:	Performance1
Next Topic:	regarding sql_id value in awr report

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Jul 01 12:17:18 CDT 2024