We have an SSIS package that builds a large analysis services cube by doing a "full process" of the cube. The SSIS package normally is executed by a scheduled agent job. This arangement has been in production for a year and had worked well until
recently. We use SQL Server 2008 and Windows Server 2008.
Recently, the SSIS package has been having problems when run by the agent job. The agent job executes the SSIS package and the agent job reports that the job ended successfully. However, the cube has not been usable because the
measure group partitions are indicated as "unprocessed". We also have determined that the pre-existing fact files in the ".prt" folder are being deleted by the SSIS package but are not being recreated by the package as they should.
This doesn't happen if we execute the SSIS package directly. If we open the Integration Services server and run the cube-builder package, everything performs as it always has and the cube is fully processed. When the SSIS package is run directly,
it executes significantly longer than if run through the agent job, and we are convinced this is because the measure groups are being created. We have repeated our testing enough to know that the measure groups always are proc
View Complete Post