Skip to main content
The processing order in the Reporting Service is a little different than I expected. We insert a bulk of records in the table rapport_queue to have them printed. The documents are printed in a random order. When looking into the table rapport_queue we can see the following: the insert_date_time is in the same order as the ID. But the update_date_time is in a different order. Is it possible to influence the order of processing and or what causes this behaviour?



ID insert_date_time update_date_time

133 2019-08-07 12:32:35.843 2019-08-07 12:32:46.263

134 2019-08-07 12:32:35.850 2019-08-07 12:32:44.320

135 2019-08-07 12:32:35.853 2019-08-07 12:32:44.310

136 2019-08-07 12:32:35.860 2019-08-07 12:32:44.277

137 2019-08-07 12:32:35.863 2019-08-07 12:32:46.233

138 2019-08-07 12:32:35.870 2019-08-07 12:32:45.750

139 2019-08-07 12:32:35.877 2019-08-07 12:32:45.757

140 2019-08-07 12:32:35.883 2019-08-07 12:32:45.703

141 2019-08-07 12:32:35.887 2019-08-07 12:32:46.823



FYI: we use the Reporting Service 3.2.0.0.
Hi Hugo,



The report service can be configured to process multiple reports asynchronously. A slow report might be finished later than a fast report. It is quite likely the update_date_time probably shows when the report was finished processing, not when it started.



The order in which they start is determined by the order they are returned from the rpt_get_reports procedure. You can change the order in which reports are started in this procedure, by adding an explicit order-by clause to the select statement that returns the reports.
Hi Anne,



Thanks, the explicit order by clause worked.

Reply