| Improving materialized view performance [message #177776] |
Fri, 16 June 2006 09:15  |
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 #177903 is a reply to message #177849] |
Sat, 17 June 2006 10:47  |
 |
Littlefoot
Messages: 21823
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?)?
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
