PS2003 OLAP cube build/transaction log size issues

[riccadonna63]

Hello

We are having major problems with our cube build. We are holding 2
years worth of data and our database size limit is currently 14Gb but
our transaction log keeps exceeding that and therefore our cube stops
building and people lose access with the following error message "An
internal server error has occurred and Project cannot log you on at
this time. Please try again later. (5015)" Once the log is cleared
they can access again but as soon as we start to build the cube again
the problem reoccurs.

One option is to remove all our closed projects from PS but we then
lose the functionality of doing last year vs this year comparisons
etc.

Does anybody have any suggestions on what we can do or maybe it's
something in our configuration. I would really appreciate any help at
all as I don't know where else to look or go.

Thank you
Rosa

 

[Marc Soester [MVP]]

Hi Rosa,

your problem is not Proejct Server I believe but your transaction log on the
Database. You should ask your Database Administrator to cleiar the log file
every time he/she makes a database backup. That should avoid "blowing up"
your log file

Hope this helps

 

[riccadonna63]

Hi Rosa,

your problem is not Proejct Server I believe but your transaction log on the
Database. You should ask your Database Administrator to cleiar the log file
every time he/she makes a database backup. That should avoid "blowing up"
your log file

Hope this helps
--
Marc Soester [MVP]
State Manager: EPMhttp://marcsoester.blogspot.com









- Show quoted text -

Hi Marc

Thanks for your reply. The transactin log is cleared everytime a
backup is done but we have to keep increasing the database size all
the time to cope. They tell me that 14Gb is a huge limit to have
allocated and we can't just keep increasing the limit all the time.

I know it varies on the amount of projects etc but is there a
recommended/normal range for the database limit?

Thanks
Rosa

 

[Marc Soester [MVP]]

Hi Rosa,

I agree with your IT staff, 14 GB seems a lot for project server.

If the log file is that big and not the tables, then I would assume that the
backup does not clear the transaction log and this is still my assumtion by
the way. Only backing up the DB will not clear the transactional log.

I would recommend to clear the log file. Then monitor the increase of the
log file every day and after each backup. I bet that the log file does not
reduce in size after the backup. If this is the case then your DB's need to
look into their backup.
Hope this helps
--
Marc Soester [MVP]
State Manager: EPM
http://marcsoester.blogspot.com

 

[riccadonna63]

Hi Rosa,

I agree with your IT staff, 14 GB seems a lot for project server.

If the log file is that big and not the tables, then I would assume that the
backup does not clear the transaction log and this is still my assumtion by
the way. Only backing up the DB will not clear the transactional log.

I would recommend to clear the log file. Then monitor the increase of the
log file every day and after each backup. I bet that the log file does not
reduce in size after the backup. If this is the case then your DB's need to
look into their backup.
Hope this helps
--
Marc Soester [MVP]
State Manager: EPMhttp://marcsoester.blogspot.com









- Show quoted text -

Thanks Mark

I will ask our IT guys to monitor as you've suggested.

Cheers
Rosa

 

[winzigm]

Hi MPS 2003 can be configured with splitted databases, so you can can
splitted your DB to several parts as is described here

http://office.microsoft.com/en-us/projservadmin/HA011654031033.aspx

and then you will be able set transaction logging on DB with
MSP_CUBE_* tables to simple.