R
Rickard
We've been using the timesheet function in PWA 2007 for a couple of years
now, and lately we've noticed it takes a very long time for a user to create
a new timesheet. It's probably because of all the old timesheets stored in
the Project Server databases, so we're planning to delete some of them (in
Server Settings - Delete Enterprise Objects - Timesheets). My question is;
could this have any effect on our published projects actual work (the
timesheet data has been imported to the projects tasks earlier and maybe some
kind of synchonization will delete the data as well)?
Another question; we need to create copies of some of the timesheet tables
(in the Project Server 2007 Reporting database) before removing the old
timesheets because the data needs to be included in many of our SQL Reporting
Services reports. Is it okay to create these "copies" in the Reporting
database or could that mess up anything?
now, and lately we've noticed it takes a very long time for a user to create
a new timesheet. It's probably because of all the old timesheets stored in
the Project Server databases, so we're planning to delete some of them (in
Server Settings - Delete Enterprise Objects - Timesheets). My question is;
could this have any effect on our published projects actual work (the
timesheet data has been imported to the projects tasks earlier and maybe some
kind of synchonization will delete the data as well)?
Another question; we need to create copies of some of the timesheet tables
(in the Project Server 2007 Reporting database) before removing the old
timesheets because the data needs to be included in many of our SQL Reporting
Services reports. Is it okay to create these "copies" in the Reporting
database or could that mess up anything?