Refresh Data In Cube

Hi,
How to refresh data for a day in a cube. I want to do this without deleting
the records from the fact tables for the specified day.
Regards,
Yash
You do this with an incremental build of the cube... You must be able to
write a sql expression which identifies WHICH rows in the fact table are
new. If you allow rows to come in twice your cube data will be inaccurate.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Yash" <Yash@.discussions.microsoft.com> wrote in message
news:8909B51B-58CB-48FD-BF42-3E226354B578@.microsoft.com...
> Hi,
> How to refresh data for a day in a cube. I want to do this without
deleting
> the records from the fact tables for the specified day.
> --
> Regards,
> Yash
>

Refresh cube after data changed?

After I created a cube in BI Studio, I added more data to the fact table, modified dimension table, and refreshed DSV. I got Refresh Data Source View message ‘No changes have been found’, but I didn’t see the data that I just added in from cube browser.

(Database connecting and database structure didn’t change)

My questions:

1. Is refresh DSV only for database structure change?
2. Which step I was missing for refreshing cube data?

Thanks in advance.

Yes, refreshing is to pull database structure changes into the DSV. To get the new data, "Process" the cube.

You'll find that MSAS provides a rich set of capabilities and abilities to update the data. For now, always do a "Full Process", until you get more comfortable with the technology. Depending on the size of your cube, plan on spending a little time learning about incremental processing and partitions. For anything other than small cubes, expect to define / manage partitions are part of the definitions. The impact on performance is dramatic.

|||Thank you very much Dave.

It is very helpful information.

Refresh cube after data changed?

After I created a cube in BI Studio, I added more data to

the fact table, modified dimension table, and refreshed DSV. I got Refresh Data

Source View message ‘No changes have been found’, but I didn’t see the data that

I just added in from cube browser.

(Database connecting and database structure didn’t change)

My questions:

1. Is refresh

   DSV only for database structure change?

2. Which

   step I was missing for refreshing cube data?

Thanks in advance.

Yes, refreshing is to pull database structure changes into the DSV. To get the new data, "Process" the cube.

You'll find that MSAS provides a rich set of capabilities and abilities to update the data. For now, always do a "Full Process", until you get more comfortable with the technology. Depending on the size of your cube, plan on spending a little time learning about incremental processing and partitions. For anything other than small cubes, expect to define / manage partitions are part of the definitions. The impact on performance is dramatic.

|||Thank you very much Dave.

It is very helpful information.

Refresh cube after data changed?

After I created a cube in BI Studio, I added more data to the fact table, modified dimension table, and refreshed DSV. I got Refresh Data Source View message ‘No changes have been found’, but I didn’t see the data that I just added in from cube browser.

(Database connecting and database structure didn’t change)

My questions:

1. Is refresh DSV only for database structure change?
2. Which step I was missing for refreshing cube data?

Thanks in advance.

Yes, refreshing is to pull database structure changes into the DSV. To get the new data, "Process" the cube.

You'll find that MSAS provides a rich set of capabilities and abilities to update the data. For now, always do a "Full Process", until you get more comfortable with the technology. Depending on the size of your cube, plan on spending a little time learning about incremental processing and partitions. For anything other than small cubes, expect to define / manage partitions are part of the definitions. The impact on performance is dramatic.

|||Thank you very much Dave.

It is very helpful information.

Referencing 2 dimensions

Hi all,

I hope someone can see a way around this.

I have a cube which is working well an need to add a new dimension. The new dimension does not have a reference to the fact table but refers to 2 current dimensions.

Is there a way of adding in the new dimension referencing the current dimensions, or will I need to go to the database and add a new foreign key to the fact table?

Thanks in advance,

David

Hi,

You can create a snowflake schema:

http://msdn2.microsoft.com/en-us/library/ms345139.aspx

http://sqljunkies.com/WebLog/sqlbi/archive/2005/10/07/17040.aspx

Regards|||

Thanks Lucas.

I knew I wanted a many-to-many relationship, but didn't think of adding an extra Measure to do it.

Regards,

David.

referenced relationship error

I try to add dimension with referenced relationship. I defined everything like explaination in Books online, but when I try to save cube, I always get message:

"Cube 'Cube' cannot be saved because of the following errors:

Errors in the metadata manager. The 'Key' intermediate granularity attribute of the'IntDim'

measures group dimension does not have an attribute hierarchy enabled."

I enabled this attribute hierarchy for Key... but....

Anybody who can help?

When I tried these basic steps using the Adventure Works sample it worked for me. If you remove the dimension relationship and try to re-create it after saving the dimension with the key enabled, does the problem still occur? If so, could you send me the project files in a Zip?|||

How my problems started...

First of all, when I migrate OLAP DB, in one cube I had relation (referenced) by two fields in tables. I don't know is it supported in AS 2005. I think no.

This is my main question.

After that I try to do several different thinks, explaned in Books on-line (attributes, new named calculation...), but without good results... Unfortunatly, I spend two days to solve this problem, end on the end I changed this relationship between tables (replaced referenced with regular relationship) on the AS 2000 and made migrated again.

At the moment I have not project because I made new migration, but I will try to re-create all story and send to you..

I send to me proper your e-mail adress

|||

Here's my email. Just replace the "-" with an "@.".

Matt.Carroll-Microsoft.com

|||

Matt Carroll wrote:

Here's my email. Just replace the "-" with an "@.".

Matt.Carroll-Microsoft.com

Or you can send it directly to me. "Sasha.Juric" with same domain name as Matt's.

|||When I try to do it from the beginning, everything is ok. But when I migrate old Datebase in AS, I have problem. when i have time I re-craete it. But stay the question, if I use two fields in referenced relationship, does AS 2005 support it

referenced relationship error

I try to add dimension with referenced relationship. I defined everything like explaination in Books online, but when I try to save cube, I always get message:

"Cube 'Cube' cannot be saved because of the following errors:

Errors in the metadata manager. The 'Key' intermediate granularity attribute of the'IntDim'

measures group dimension does not have an attribute hierarchy enabled."

I enabled this attribute hierarchy for Key... but....

Anybody who can help?

When I tried these basic steps using the Adventure Works sample it worked for me. If you remove the dimension relationship and try to re-create it after saving the dimension with the key enabled, does the problem still occur? If so, could you send me the project files in a Zip?|||

How my problems started...

First of all, when I migrate OLAP DB, in one cube I had relation (referenced) by two fields in tables. I don't know is it supported in AS 2005. I think no.

This is my main question.

After that I try to do several different thinks, explaned in Books on-line (attributes, new named calculation...), but without good results... Unfortunatly, I spend two days to solve this problem, end on the end I changed this relationship between tables (replaced referenced with regular relationship) on the AS 2000 and made migrated again.

At the moment I have not project because I made new migration, but I will try to re-create all story and send to you..

I send to me proper your e-mail adress

|||

Here's my email. Just replace the "-" with an "@.".

Matt.Carroll-Microsoft.com

|||

Matt Carroll wrote:

Here's my email. Just replace the "-" with an "@.".

Matt.Carroll-Microsoft.com

Or you can send it directly to me. "Sasha.Juric" with same domain name as Matt's.

|||When I try to do it from the beginning, everything is ok. But when I migrate old Datebase in AS, I have problem. when i have time I re-craete it. But stay the question, if I use two fields in referenced relationship, does AS 2005 support it

Re-Engineer an Existing CUBE

Is it possible to bring a deployed CUBE into Visual Studio.NET?

My CUBE is deployed on SQL 05 Analysis Services. It is the "Portfolio Analyzer" CUBE shipped with Project Server 07.

|||

You can do it one of two ways:

1. File... Open... Analysis Services Database

2. File... New... Project... Business Intelligence Projects... Import Analysis Services 9.0 Database

You might see the Project REAL recommendations regarding your different options under the "Three Ways to Interact With Analysis Services" section of: http://www.microsoft.com/technet/prodtechnol/sql/2005/realastd.mspx

|||I can bring it into VS.NET but the measures are not associated with any Data Source views. Any idea?|||

Hmm. Maybe the cube is processed via push-mode? But even then, I thought you still had to tie a measure to a column in the data source view. So you don't see any data source views in the project?

After you do the Import command I mentioned, look on disk and open up the .cube and .partitions file in Notepad and do a search for "select " (that's select <space>) and see if you can see any out-of-line bindings. That might be how they do it.

Reduce time connection to AS2005

what is "slow"?
when the pivottable access the cube, the first time a query is executed
against the server to retrieve the measure names, but this query also ask
for the data, not only the labels. (use the profiler to see this query)
if 1 of your measures is a complex one, then you'll suffer a delay.
if your metadata is more complex in your cubes, then the time required to
retrieve the metadata is longer.
verify if you have the right SP level installed on the server AND the client
verify if you have activated the compression
also, it could be an authencation issue, maybe you suffer a delay due to a
network configuration issue (verify the DNS configuration if you use the
Active Direcotry)
again, use the profiler on the server to identify the source of the problem.
"Kazmane" <mkazmane@.capinfo.co.ma> wrote in message
news:%23y9YKXulGHA.1972@.TK2MSFTNGP05.phx.gbl...
> can someone help to reduce a time connecting to As2005 with using OLEDB9.0
> and PivotTable.
> thanks.
>can someone help to reduce a time connecting to As2005 with using OLEDB9.0
and PivotTable.
thanks.|||what is "slow"?
when the pivottable access the cube, the first time a query is executed
against the server to retrieve the measure names, but this query also ask
for the data, not only the labels. (use the profiler to see this query)
if 1 of your measures is a complex one, then you'll suffer a delay.
if your metadata is more complex in your cubes, then the time required to
retrieve the metadata is longer.
verify if you have the right SP level installed on the server AND the client
verify if you have activated the compression
also, it could be an authencation issue, maybe you suffer a delay due to a
network configuration issue (verify the DNS configuration if you use the
Active Direcotry)
again, use the profiler on the server to identify the source of the problem.
"Kazmane" <mkazmane@.capinfo.co.ma> wrote in message
news:%23y9YKXulGHA.1972@.TK2MSFTNGP05.phx.gbl...
> can someone help to reduce a time connecting to As2005 with using OLEDB9.0
> and PivotTable.
> thanks.
>