Project Server Help, FAQs, Blogs, and HowTos
This is The Header Then

Maintenance Plans for Project Server 2007 DBs

posted January 3rd, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 4.33 out of 5)
Loading ... Loading ...

As I’ve previously discussed, at my present client we recently were working very closely with Premier Support to resolve some issues with the cube build. Throughout the course of these discussions, I was told that I really should be running DB Maintenance Plans on the PS07 DBs because with the switch to GUIDs in Project Server 2007, the indices in the various databases can become stale very quickly.

My response to Premier was that since Microsoft has provided no guidance on doing this, and since Microsoft has made such a big deal about not touching any of the databases except Reporting (or Published in very limited circumstances) implementers (including myself) are concerned about doing ANYTHING with regards to Maintenance Plans without guidance from Microsoft.

Premier responded that Chris Fiessinger wrote a blog post about this recently. The agent I was working with gave me advice on how to set up the jobs in the maintenance plan, and promised to press the Product Group to put out some official guidance in the near future.

Discuss this post on the EPMFAQ Blog Posts Forum.

Related Posts

Slow or Failing Cube Builds and Very Large TempDB

posted December 29th, 2007 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5 out of 5)
Loading ... Loading ...

At my present client, prior to the release of Project Server 2007 SP1, we obtained and deployed the hotfix rollup described in KB939594 to resolve some of the issues present in the product prior to the release of SP1.

Unfortunately, after deployment of this hotfix we discovered that when building the cube it would take significantly longer than RTM to build. Specifically:

  • Cubes built with earliest start and latest finish would take an hour and a half or more to build
  • Cubes built with a timeframe of 36 months forward and 13 months back 7+ hours to build and would cause the TempDB to get HUGE (in excess of 200GB)

When running the Cube Build without a date range, the cube would build in an hour or two — but as soon as you introduced a date range, the cube build would jump to 7+ hours, if it was even successful at all. More often than not, however, it would simply grow the TempDB to around 250GB, filling up the disks that the SQL databases were stored on and fail.

Discuss this post on the EPMFAQ Blog Posts Forum.

Related Posts

The opinions expressed on this site by the authors and those providing comments are theirs alone, and do not reflect the opinions of the respective employers of the authors or any employee thereof. Our respective employers are not responsible for the accuracy of any of the information supplied by on this site.

Terms of Use | Privacy Policy | Publishers

All content on this website is covered by the
Creative Commons Attribution-Share Alike 3.0 United States License.
Theme ©2007 The Heckerped WordPress Theme created by JTk of Doc5 under the Creative Commons Attribution License.