AS2005 Cube Processed "Successfully", But Data Not Refreshed

We process the cube automatically every night but the data isn't up-to-date despite a "successful" processing.

However, if I go onto the server and process the cube directly there through the BI Dev Studio, the data will finally get updated.

Similarly, if I try to process the cube from a client using Management Studio, it processes "successfully" as well, but the data is not updated.

I have to do it on the server itself. I've noticed this behavior the last few weeks, but it could very well have been going on for quite some time.

Any ideas or thoughts on this behavior?

What method you use in your processing automation?
Are you using SSIS processing Task?

Try and run SQL Server Profiler trace to capture Command Begin/End requests only and try to see if one is issued during your nightly processing job.

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

|||I was told that we do indeed using SSIS Processing Task for the nightly cube processing automation.

I just ran a profile trace and I don't think I see any real difference in the Command Events whether I process the cube in the BI Dev Studio directly on the server or from SQL Management Studio from a client. However, the data is usually only updated if I do it on the server directly (and I always use the BI Dev Studio).

What should I be looking for in the trace?
|||I think I know what's going on. When I do it in the BI Dev Studio on the server, I'm essentially processing the solution as a whole. As a result, when the process screen comes up, the Type is database. If I processed the cube and not necessarily the entire solution, the Type is Cube.

I hope that make sense.

Which "should" be the correct one to use and what's the difference? It appears in our case, the "Database" type is correct.

|||

Can you connect using MDX Sample application?

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