Re: dimension table
Date: Tue, 8 Dec 2009 12:18:09 -0800 (PST)
Jared is right, we need a few details here, (and more would be better...)
-What's the current description of the table, vs. the source tables its based on?
-What do the main troubling queries look like, including explain plans? It may have more to do with the SQL than the table design.
-A dimension table is a commonly the main columns duplicated then used to build your fact tables from. They should be fast and hit hard, so we need to see how they are joined in the explain plans, it could even be a matter of CBO issues.
"Go away before I replace you with a very small and efficient shell script..."
- On Tue, 12/8/09, Kar <kp0773_at_gmail.com> wrote:
From: Kar <kp0773_at_gmail.com>
Subject: dimension table
Date: Tuesday, December 8, 2009, 12:17 PM
I am observing the date dimension table is giving high cpu cost and on explain table it seems to be a troubling spot .
I am looking for any suggestion on what would be a better approach for designing this table .
Appreciate any suggestions.
http://www.freelists.org/webpage/oracle-l Received on Tue Dec 08 2009 - 14:18:09 CST