Showing posts with label as2005. Show all posts
Showing posts with label as2005. Show all posts

Tuesday, March 20, 2012

Processing options in AS2005

I'm trying to get my hand around these new fangled processing options in SSAS2005 and have read TK Anand's excellent paper on the subject: http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsql90/html/sql2k5_asprocarch.asp.

Unfortunately I can't see the wood for the trees so here's a question. Is it possible to selectively remove data from a partition? i.e. Without doing a ProcessFull or ProcessClear

Here's the scenario for which i need this:

We have a cube into which we are loading returns (the nature of these returns is unimportant) submitted from external organizations. Each return can go through a series of statuses:

Submitted Received Accepted Approved Superceded

They want to see data for all 'Approved' returns. That's easy. However, a return becomes 'Superceded' we want to remove it from the cube. Is that possible? I don't want to have to do a full process every night because there is a huge amount of data and our processing window is small.

Thanks

Jamie

You have several ways to handle this problem.

One you can partition the data in your cube down futher. Creating several partitions. If you know range of data might change, create a separate parittion (or few partitions) for it .

Processing less data and processing in parralel should go way faster.

Second.

If you dont have many changes happening into your data. You just need to correct value for some transactions. You can enable Writeback for you measure group. Using Writeback you can "poke" 0 into any cell in multidimensional cube space. For instance you can zero out value of sales for User A on Day D.
Internally Analysis Serivces creates ROLAP partition where it writes corrective values.
You client application needs to be able to handle udates correctly. There are quite a few issues with writing into non-leaf cells.

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

|||

Thanks Edward,

We were definately thinking of going down the partitions route so its good to get some confirmation of that approach.

Writing back from the client app is a no-no though - for reasons I won't go into.

-Jamie

Processing of AS2005 cube from Integration Services package: Operation completed with 882 proble

Hi!

I did not now if I should post it in the Integration Services forum, but I believe this post is more AS related. Anyway, I am processing my cubes in SSIS after some loading of data. I use the SSIS log provider for SQL Server to log errors, and I get the following error message in the message column of a row in sysdtslog90:

"Server: Operation completed with 882 problems logged."

I wonder, where can I find this log? Is there some default location in AS or do I have to enable another log event than OnError or OnWarning in SSIS?

Thanks!

I'm guessing I'm looking for the Dimension key error log path when it is set for (default).

I found something here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1284202&SiteID=1

Seems like you have to set the location in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config\msmdsrv.ini. Now I get a key error logfile, but it is empty =/. I've restarted the AS service and set the ErrorLog elements in the ini to:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4</ErrorLogFileSize>
<KeyErrorAction>0</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>0</KeyErrorLimit>
<KeyErrorLimitAction>0</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>0</KeyDuplicate>
<NullKeyConvertedToUnknown>0</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

I've also tested the following without success:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4000000</ErrorLogFileSize>
<KeyErrorAction>1</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>1</KeyErrorLimit>
<KeyErrorLimitAction>1</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>1</KeyDuplicate>
<NullKeyConvertedToUnknown>1</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

More info here, but it does not get you that much wiser: http://technet.microsoft.com/en-us/library/ms174827.aspx

Seems like you do have to set the ErrorLog properties manually for each cube (Process > Change Settings > Use custom error configuration).