Processing one 'fact partition or measure group' weekly, while others are daily?

Is this possible to have done in 2 different (or 1 intelligent) AS deployment script(s)? Sunday would be the full processing day, while other days would just handle the smaller fact areas.

You could use Integration Services with XMLA scripts to accomplish this...

Frank

|||

Is this type of thing something that's available in standard edition? I tried making a new connection with type of Integration Services, but I'm not sure where to go from there, as the object exlorer appears to give no options to make a new package or whatever route I'd need to take to make a new schedule.

Could you provide more info as to how it would be created and then scheduled (or is this a manual thing if not an option provided by SSIS)?

|||

Yes, this is available in the standard edition.

how to create an SSIS package: http://msdn2.microsoft.com/en-us/library/ms141178.aspx

This thread explains a couple of different ways to do this: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1626707&SiteID=1

Frank|||

I will take a look over the article. Thanks.

I also want to ask again, is it possible to process all fact tables but one (not by specifying the name of the facts, but only the name of the one I don't want to process)?

Processing measure groups together using same dimensions

Hi,

2 separate measure groups of a cube are being processed with 2 separate SSIS packages and these measure groups use same dimensions of the cube. SSIS packages are used to handle the partitions. Would there be a conflict if the SSIS packages both attempt to Process the same dimensions (update/full process) at the same time?

How does Analysis Services 2005 handle this? Does one wait for the other and then the 2nd package skips the Dim process or reprocesses it?

In such cases, is there a need to have a SSIS package that processes only the dimensions 1st and then the other 2 packages start off parallely to process the 2 measure groups without touching the dims.

Regards

You can process the dimension first in one step and after this processing have succeded you can process the two measure groups partitions in parallell.

Your last alternative sounds correct.

Regards

Thomas Ivarsson.

ProcessAdd processing hangs

I'm trying to do an incremental process of a cube that has 3 measure groups. The first measure group is fairly straightforward, run-of-the-mill measures. The other 2 are distinct counts of an ID.

When running the incremental process (ProcessAdd), the status seems to complete, and then everything just hangs. I can't find anything that the server is doing, but it won't return. This happens in BIDS using debug, management studio wizard, and management studio XMLA execution windows.

Sometimes I can get the first measure group to return... Once the 3rd returned. The 2nd has never worked.

Thoughts on what's happeneing? Does anyone know how to see what's going on in the background? I have a SQL trace going and a trace on the SSAS server, and nothing seems to be going on...

Thanks!
-DougI have a similar issue occurring. I have an SSIS package that uses an analysis services task to incrementally update the most recent partition in three measure groups. It hangs everytime when run under the SQL agent Job engine, however, it processes fine through the SSIS debugger in BIDS.

I think I'm going to try submitting the XMLA statement directly from the job rather than going through SSIS. Did you ever figure out the issue you were seeing?|||

Try and run Profiler against Analysis Server and see if there is any activity is goign on.

Make sure you've got latest service pack installed. And lastly: if the problem still persists, contact product support services and report it.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

ProcessAdd processing hangs

I'm trying to do an incremental process of a cube that has 3 measure groups. The first measure group is fairly straightforward, run-of-the-mill measures. The other 2 are distinct counts of an ID.

When running the incremental process (ProcessAdd), the status seems to complete, and then everything just hangs. I can't find anything that the server is doing, but it won't return. This happens in BIDS using debug, management studio wizard, and management studio XMLA execution windows.

Sometimes I can get the first measure group to return... Once the 3rd returned. The 2nd has never worked.

Thoughts on what's happeneing? Does anyone know how to see what's going on in the background? I have a SQL trace going and a trace on the SSAS server, and nothing seems to be going on...

Thanks!
-DougI have a similar issue occurring. I have an SSIS package that uses an analysis services task to incrementally update the most recent partition in three measure groups. It hangs everytime when run under the SQL agent Job engine, however, it processes fine through the SSIS debugger in BIDS.

I think I'm going to try submitting the XMLA statement directly from the job rather than going through SSIS. Did you ever figure out the issue you were seeing?|||

Try and run Profiler against Analysis Server and see if there is any activity is goign on.

Make sure you've got latest service pack installed. And lastly: if the problem still persists, contact product support services and report it.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Process Cube

I have a cube with one customer count measure that use DistinctCount Aggregate Function. My testing Environment is Window Server 2003 x64 Sp1, 300 GB of Ram, and SQL 2005 EE. When I full process the cube, I use the MS Performance tool to monitor the MSAS:Proc Aggregations. I find out the Temp file bytes written/sec has been used, but the usage of the RAM never go above 15 GB. Why the temp file still in use. When I use AS2000 I know I can adjust the Process Buffer size to avoid the use of Temp file to increase the process performance. Should I take the same action in AS2005. But my OLAP\Process\BufferMemoryLimit has been set to 60 => 180GB can be use. Why temp file still in use? Should I adjust the OLAP\ProcessPlan\DistinctBuffer too that is the new item in AS2005?

Analysis Services 2005 is quite different in the way it does processing and manages memory.

First I would recommend you look at the performance guide for some clues on how to improve processing performance. I also not sure what the real concern is: is that your are seeing Analysis Server using less memory during processing? Is that you compare AS2000 and AS2005 and you are seeing slower processing performance?

Just to note, and you might know it alreday, processing of distinct count partitions is quite different from processing of regular partitions. Same goes for querying. Records stored in distinct count partitions as stored sorted. You can even see that for processing such partition Analysis Server will send different SQL query, it will ask data from SQL Server to come in sorted order.
What I am getting at is processing and querying of distinct count partitions is quite different from regular partitions. If you wanted to optimize processing and query performance the first and most important is to make sure your partition your cube along dimension that you get your distinct count for.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||my concern is how the memory usage in AS2005. Since my server has 300GB of memory, but AS2005 doesn't use up all the memory during the process, instead it use the Temp file that can slow down the process performance.