10106-EN - When there are several thousands of projects into the database, entering timesheets can become slow.

#FAQ: 10106-EN, Date: 11/04/2008

When there are several thousands of projects into the database, entering timesheets can become slow.

The information in this article applies to :

OroTimesheet 5.x (English)
OroTimesheet 5.x (French)
OroTimesheet 6.x (English)
OroTimesheet 6.x (French)

Description

Indeed, when there are several thousands of projects entered into the database, entering timesheets (through the web interface or the standard Windows version) can become slow.

Solution

It is strongly recommended to put terminated projects (or projects that you are not planning to enter timesheets anymore) as inactive. Indeed, when entering timesheets, inactive projects are not taken into account.

For example, if you have 10 000 projects into the database and all these 10 000 projects are active, entering timesheets could be slower. However, if only 500 projects from the 10 000 projects have the status "Active", then entering timesheets will be a lot faster.

Please note that you can any time put back a project as active or vice versa.

Status

Information