When building reports with designer, the standard
process-priority for new reports is set to 5.
This means that the new report is automatically
preprocessed after a datawarehouse refresh.
Only admin can change this priority to values from 0 to 9.
Priority 0 means => no preprocessing.
Priotity 1 to 9 is from high to low.
It's better to set the preprocessing-priority for newly
build reports to 0, so they won't automatically
preprocess after a datawarehouse-refresh.
If a user selects such a reports, than the processing will
take place at that time, so the information is still
available.
And the admin has the possibility to activate
preprocessing when it is a report with frequent inquiry.
Preprocessing saves time at inquiry, because a
preprocessed reports is loaded right away to the
explorer.
Normally admin has to make choices because the system
is not able to preprocess all reports for all points (for
example: one single distributed report will process
hunderds of reports for every center and summary point
in your organisation. Allthough processing only costs a
few seconds per report, the number of occurences will
cost time before a report is preprocessed completely).
Logged In: YES
user_id=1133657
Installation instructions:
1. Unzip 1094907.zip to a working-directory
2. Launch \datawarehouse\1094907.sql with MS SQL Query
Analyzer or isql
to set the default ReportPriority to 0
3. Copy
\ProcessPriority\webfinancials\designer\builder\ACTION_SaveR
eportAS.cfm
to c:\inetpub\wwwroot\webfinancials\designer\builder
Replace the existing file
OPTIONAL:
Newly build reports are getting a processpriority 0.
Untill now the default processpriority was 5.
Only admin can change this with "manage objects".
For customers who have a lot of reports designed by several
users SQL is created
to reset the processpriority from 5 to 0 for existing reports.
Launch \datawarehouse\1094907_migrate.sql
End of instructions
Default Process Priority from 5 to 0