Ya i agree u need to look at Explain plan. here are some more point to think about.
1. MV's
2. Partations.
3. Look at OPTIMIZER_FEATURE_ENABLE = 9.0.1 0r 9.2.0
4. Disk contention if any.
Your best bet is to create two separate FACT tables. MOVIE_DEMAND and MOVIE_VIEW.
Going by Books as u are changing the granularity of your fact table us should have separate TIME demension also. But i do not see any added advantable unless u are going to do any factless reporting.
Well u will have to Build some thing called lookup and pass each record through lookup. Some thing similar to Lookup transformation. Lookup table might look like ( Actial-key TABA-Key TABB-Key TABC-Key ) Look for matching Names rest u will have to clence.
The building of lookup table is reduce...
Well MV's are far more than simple SQl version of an aggregate table. Not sure why there is referance to ETL in the previous post. MV are use more for performce improvement. I will try to explain some of the features of MV. But I strongly would recomend u read a Oracle 9i documentation Part...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.