Deleting timesheets does not remove timesheet data from the reportingdb

[Astro Boy]

We have run across a strange behavior (strange to me, at least) that
Microsoft claims is part of the MOPS 2007 design.

When you delete timesheets using PWA>Delete Enterprise Objects, the
data from those deleted teimsheets remains in the Reporting database.

Our scenario is this:

Prior to going live on MOPS, we did a lot of training using the to-be-
production system. At the end of training, we deleted all projects and
timesheets, then also deleted all timesheet periods. We then created
new timesheet periods, started loading projects, and began using new
timesheet periods to create new timesheets and report project and non-
project (Admininstrative Time Categories) time.

Now we are seeing info from the timesheets used in training appearing
in our Data Analysis views and our Reporting database.

We have a case open with Microsoft Premier Support. The engineer there
is telling us this is designed behavior. I can't imagine why this is -
delete means DELETE, right? Apparently not so here.

Can anyone explain to my why you might want to keep data from deleted
timesheets in the Reporting db? Does anyone know how to remove this
data from Reporting, or at least filter it out?

Thanks in advance!

AB

 

[Michael Brown]

AB -

I've run into the same situation as you are seeing. I was able to remove
timesheets and related timesheet periods for our 2007 calendar, but the data
still appears to exist in the reporting Database. I assume - if this WAS by
design - that Microsoft figured people might want to report on data for
extended period, but allow the data to removed from the 'production
environment' to speed things up? If that's the case, I suppose a SQL script
could be written to purge the data from the various timesheet related tables
in the reporting database. let me know if you hear an update on this!

Regards,
Michael Brown

 

[Astro Boy]

AB -

I've run into the same situation as you are seeing.  I was able to remove
timesheets and related timesheet periods for our 2007 calendar, but the data
still appears to exist in the reporting Database.  I assume - if this WAS by
design - that Microsoft figured people might want to report on data for
extended period, but allow the data to removed from the 'production
environment' to speed things up?  If that's the case, I suppose a SQL script
could be written to purge the data from the various timesheet related tables
in the reporting database.  let me know if you hear an update on this!

Regards,
Michael Brown













- Show quoted text -

A follow up to this - we've been tracking it down for some time, and
have a few, but not all, answers.

1. The "Timesheet" cube (the only OLAP cube that shows you project and
administrative time) DOES keep all timesheets, including deleted
timesheets, presumably forever. This is by design, so that timesheets
can be auditable.

2. There is no way to filter out deleted timesheet info from your Data
Analysis views. This appears to be a design flaw, although Microsoft
has yet to render a judgement on that.

The lesson here is DON'T DO YOUR TRAINING IN PRODUCTION, even if
you're not yet in production. You think you are cleaning out the
system by deleting projects and timesheets from training using
PWA>Server Settings>Delete Enterprise Objects, but you are not
COMPLETELY cleaning it out. Always use a test/training system.

I'll try to remember to update this if we get any relief from
Microsoft by way of hotfix or patch.

 

[Gary L. Chefetz]

Astro Boy:

Just curious, have you tried forcing a RDB refresh? No effect?

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

AB -

I've run into the same situation as you are seeing. I was able to remove
timesheets and related timesheet periods for our 2007 calendar, but the
data
still appears to exist in the reporting Database. I assume - if this WAS
by
design - that Microsoft figured people might want to report on data for
extended period, but allow the data to removed from the 'production
environment' to speed things up? If that's the case, I suppose a SQL
script
could be written to purge the data from the various timesheet related
tables
in the reporting database. let me know if you hear an update on this!

Regards,
Michael Brown













- Show quoted text -

A follow up to this - we've been tracking it down for some time, and
have a few, but not all, answers.

1. The "Timesheet" cube (the only OLAP cube that shows you project and
administrative time) DOES keep all timesheets, including deleted
timesheets, presumably forever. This is by design, so that timesheets
can be auditable.

2. There is no way to filter out deleted timesheet info from your Data
Analysis views. This appears to be a design flaw, although Microsoft
has yet to render a judgement on that.

The lesson here is DON'T DO YOUR TRAINING IN PRODUCTION, even if
you're not yet in production. You think you are cleaning out the
system by deleting projects and timesheets from training using
PWA>Server Settings>Delete Enterprise Objects, but you are not
COMPLETELY cleaning it out. Always use a test/training system.

I'll try to remember to update this if we get any relief from
Microsoft by way of hotfix or patch.