Home » RDBMS Server » Performance Tuning » Improving materialized view performance
Improving materialized view performance [message #177776] Fri, 16 June 2006 09:15 Go to next message
ajithgk73
Messages: 2
Registered: June 2006
Location: India
Junior Member
I am new to materialized view concept.
For our new project of a Financial accounting package, we decided to use materialized view to keep the daily balance of account heads. Also this will be based on different locations of the company. We used two materialized views for this purpose. One for asset and liability type of ledgers and another for income and expense type, as the second one needs the balnce to reset to zero on the begining of every financial year. These MV's are set to complete refres on commit of Ledger table, and Dcument posting table.

Now the problem is that the system is very slow while saving(especialy) or retrieving data from/to these tables.

Can any on suggest any specific/generic points to improve the performance of this materialized view?

We are developing this application in VB.NET and Oracle 10g server

Thanks in advance and regards
Ajith
Re: Improving materialized view performance [message #177834 is a reply to message #177776] Fri, 16 June 2006 15:15 Go to previous messageGo to next message
Littlefoot
Messages: 21808
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
How often do you refresh materialized views? Is the refresh process incremental or complete, on demand or scheduled? If scheduled, could it be done during non-working hours?
Re: Improving materialized view performance [message #177849 is a reply to message #177834] Fri, 16 June 2006 21:59 Go to previous messageGo to next message
ajithgk73
Messages: 2
Registered: June 2006
Location: India
Junior Member
The MV is Set for COMPLETE REFRESH ON COMMIT. MV is supposed to refresh as and when an entry is made to the Document(Voucher) table. This can happen very frequently

Thanks for the responce

Regards
Ajith
Re: Improving materialized view performance [message #177903 is a reply to message #177849] Sat, 17 June 2006 10:47 Go to previous message
Littlefoot
Messages: 21808
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
If it is set to perform complete refresh on commit, and if the table is large (huge?), you'll have to wait some time until refresh is done - it can take a while.

Is it necessary to do so? Would customers be satisfied if there's a delay (one day, for example?)?
Previous Topic: Automatic Shared Memory Management (ASMM) !!
Next Topic: Req. help on Temporary Tablespace
Goto Forum:
  


Current Time: Tue Apr 30 18:22:31 CDT 2024