Re: LIMIT OF FACT TABLE DATA

• Previous message: Adam Machanic: "Re: Time for my yearly question:"
• In reply to: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Next in thread: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Reply: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Messages sorted by: [ date ] [ thread ]

Date: Fri, 23 Jul 2004 00:02:01 -0700

Answer to Fernando Questions.
1. My cube fact and dimension tables are in Oracle Database.
2. Yes I am using Foreign keys between fact and the dimension tables (the snowflake schema).

-- 
Thanks
Akber.
"Fernando Ponte" wrote:
> Two questions.
> - Are your cube Fact and Dimension tables in an Oracle or SQL Server databases?
> 
> - Are you using Foreign Keys between the Fact Table and the Dimension tables in your Cube (Star or Snowflake) Schema? If no. You need to check the T-SQL results to see if the row counts match the row counts of your fact table (it must be the same to ensure that all data from fact table was loaded to the cube)
> 
> As Dave Wickert said. Enable the system-wide processing log file and check the results. This is the best way to find more information about your cube processing.
> 
> Best Regards.
> -- 
> Fernando Ponte
> 
> 
> 
> "Dave Wickert [MSFT]" wrote:
> 
> > There is no limit on the size of the fact table in Analysis Services. To use
> > a coined by Carl Sagan, I've seen partitions with BILLIONS and BILLIONS of
> > fact rows in them.
> > 
> > I would suggest that you look at some of the suggestions raised in the
> > Analysis Services Operations Guide
> > http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
> > One of its recommendations (in the section titled "Processing Log File") is
> > to enable the system-wide processing log file option and retain long term
> > history of the processing done on your system. In the log file are all of
> > the processing requests, the SQL statement used and the final row counts
> > resulting from processing.
> > -- 
> > Dave Wickert [MSFT]
> > dwickert@online.microsoft.com
> > Program Manager
> > BI SystemsTeam
> > SQL BI Product Unit (Analysis Services)
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > 
> > "Akber" <Akber@discussions.microsoft.com> wrote in message
> > news:0BC3A29C-C530-45CF-98CA-B4899C12CF5F@microsoft.com...
> > > My Warehouse Data is basically in Oracle and I am using SQL Server DTS for
> > ETL and SQL Server Analysis Services for viewing the cube.
> > >
> > > I dont think so that the cube joins are the problem because the same cube
> > was working fine previously. I think that there is some MOLAP memory issue
> > in the Analysis Server.
> > > Well I can try ur steps but how I can grab the T-SQL that Analysis Server
> > sends to SQL Server while processing the cube
> > > -- 
> > > Thanks
> > > Akber.
> > >
> > >
> > > "Akber" wrote:
> > >
> > > > I am using MOLAP storage for my cube.
> > > > The problem which I am getting is that the cube stops showing the data
> > for the month which it was showing correctly previously. I have populated my
> > fact table with the data from the previous year i.e: from JUN 2003 till
> > todate and is being updated every year. Last week the cube was displaying
> > the data correctly for all the months but now it is not displaying any
> > figures for the 2003 although my fact table in the database has data
> > corresponding to that period. I am using full process method to process the
> > cube.
> > > > Whats the solution ?
> > > > Is there any size limit on the MOLAP type cude data storage ? Might be
> > that is the main problem but not sure. You gurus must be knowing best.
> > > >
> > > > -- 
> > > > Thanks
> > > > Akber.
> > 
> > 
> > 

• Previous message: Adam Machanic: "Re: Time for my yearly question:"
• In reply to: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Next in thread: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Reply: Fernando Ponte: "Re: LIMIT OF FACT TABLE DATA"
• Messages sorted by: [ date ] [ thread ]