M
Micah
MS Project 2007 SP2 - SQL 2005 SP3 CU1 - Analysis Services 2005 SP3 CU1
My OLAP cube builds started failing saying it was filling up tempdb. (our
tempdb is 10GB) After reading every blog I could find about this issue, I
found Microsoft labled this a known issue. The hotfix they say it is related
to is 942444 which is included in SP2 CU 6 for SQL 2005. I'm assuming we have
this in SP3. The other issue pointed out was that there needed to be some
trace flags set to resolve this. I think it is important to note that tempdb
was filling up and OLAP cubes were failing in only a few minutes. I had our
DBA set these trace flags and now the OLAP cube never finishes processing. In
a matter of minutes, the queue tell me the job is 50% complete, but says the
same thing 5 hours later.
Side note - Resource capacity set as 1 month behind and 12 ahead. 2000
resources. 32 Projects with dates ranging 2005 to 20013. Configuration
include earliest project start and latest finish.
We opened a ticket with MS, They had me set date range to 1 month behind and
1 month ahead and it built successfully in minutes. Set date range back to
earliest/lates, and it built successfully in about 15 minutes. Now that he is
not on the phone, I cannot repeat this. I can still get 1 month ahad and
behind to build but not my big one. Has anyone else had similar issues? Do I
really have more data then my tools can process?
Thanks in advance,
Micah
My OLAP cube builds started failing saying it was filling up tempdb. (our
tempdb is 10GB) After reading every blog I could find about this issue, I
found Microsoft labled this a known issue. The hotfix they say it is related
to is 942444 which is included in SP2 CU 6 for SQL 2005. I'm assuming we have
this in SP3. The other issue pointed out was that there needed to be some
trace flags set to resolve this. I think it is important to note that tempdb
was filling up and OLAP cubes were failing in only a few minutes. I had our
DBA set these trace flags and now the OLAP cube never finishes processing. In
a matter of minutes, the queue tell me the job is 50% complete, but says the
same thing 5 hours later.
Side note - Resource capacity set as 1 month behind and 12 ahead. 2000
resources. 32 Projects with dates ranging 2005 to 20013. Configuration
include earliest project start and latest finish.
We opened a ticket with MS, They had me set date range to 1 month behind and
1 month ahead and it built successfully in minutes. Set date range back to
earliest/lates, and it built successfully in about 15 minutes. Now that he is
not on the phone, I cannot repeat this. I can still get 1 month ahad and
behind to build but not my big one. Has anyone else had similar issues? Do I
really have more data then my tools can process?
Thanks in advance,
Micah