Document toolboxDocument toolbox

14.1 sp530_optimizer_runs

Owned by Billy Sewell (Unlicensed)
Jan 26, 2024

This table contains details of when the Optimizer was run.


Entries are only added to this table if the system parameter with value opt_stats_enabled is set to 'YES'. 

HouseKeeping

This table is tidied by sp_dbtidy's Audit group

 

Table Definition

Field
Type
Default
Nullable
optimizer_run_nonumber(9) (error)
resp_unit_nonumber(4) (error)
range_startdate (error)
range_enddate (error)
start_timedate (error)
end_timedate (tick)
num_engineersnumber(4) (error)
num_tasksnumber(4) (error)

Keys

primary key (optimizer_run_no) 
foreign key (resp_unit_no) references sp058_responsibility_units(resp_unit_no)

Column Descriptions

FieldDescription
optimizer_run_noServiceOptimizer-generated unique identifier.
resp_unit_noFRU
range_startFirst date of the period over which the Optimizer ran. (Time component is N/A).
range_end Last date of the period over which the Optimizer ran. (Time component is N/A).
start_time Date and time at which the Optimizer run started - uses FRU Time Zone.
end_timeDate and time at which the Optimizer run ended. Will be null while an optimizer is running - uses FRU Time Zone. 
num_engineers 

Number of engineers included in this optimizer.

This is actually the number of "resources" considered by an optimizer run and is the number of working days within the optimizer period. So for example if an optimizer is running over a period of two days and all operatives are on shift on both those days, then num_engineers is actual equal to 2x number of operatives. 

num_tasksNumber of activities included in this optimizer. This includes tentative jobs, fixed jobs and Standard Activities.