Project Server 2003 database problem

[mr.lahey]

Hi,

We've got a database with 60 fairly small projects in it (we only started
putting data in a few weeks ago) which has suddenly grown to over 60Gb in
size. The problem seemed to start yesterday when the Vwnotify service was
using 100% cpu for a long period. Restarting the views notification service
didn't fix this so I just left it to get on with it. Looking at the database
I've got a few tables with a lot of rows in them:

MSP_CUBE_RES_AVAIL_FACT - 1058152 rows
MSP_VIEW_PROJ_TASK_TP_BY_DAY - 568857 rows
MSP_VIEW_RES_TP_BY_DAY - 1060284 rows

The OLAP cube build which runs overnight and usually finishes within a hour
still seems to be running this morning 11 hours later.

I'm not sure what is going on here. We are running Project Server 2003 with
SP1. The SQL server is standard edition.

Thanks,

Jim

 

[Gary L. Chefetz [MVP]]

This sounds like you have one or more projects with serious data anomalies.
Has anyone created heavily resourced project extending over 10 to 20 years?
What project was published when you noticed the views service taking too
much time?