_Jobs

The _Jobs table contains descriptions of the jobs to be executed. Multiple jobs are stored in the table. One row describes one job.

This table describes _Jobs:

Column Type Description
JobId Big Integer Sequential key identifying job and ordering jobs.
JobType Integer Enumerator for kind of job:
  • 1 = Load Dimension
  • 2 = Create Cube
  • 3 = Load Facts
  • 4 = Set Cube Properties
  • 5 = Set Dimension Properties
  • 6 = Fill Dimension Attributes
  • 7 = Set Cube Rules
  • 8 = Load Subsets
  • 9 = Clear Cube Region
  • 10 = Delete Dimension
  • 11 = Delete Cube
  • 12 = Set Dimension Level Names
  • 13 = Load Dimension Create DAC
  • 14 = Load Elements
  • 15 = Set Attribute Driven Hierarchies
JobObject String(71) The dimension or cube that the job operates on for job types 1, 2, 4, 5, 6, 7, 8, 10 , 11, 12, 13, 14, 15. For job types 3 and 9, this is set to JobObject of FactLoadParameters.
JobParameter Integer Key to _JobsParameters table, which gives element filter information for job.
JobGroup String(100) Reports that display error logs use the JobGroups column to combine multiple jobs. This information is not processed.

Job groups are used to keep extra information on how jobs are grouped together. This information is not processed.
Started DateTime Start date-time of process.
Completed DateTime Completion date-time of process
Status Integer Completion status of process. This is the integer error status from the kernel:
  • 0 = Success
  • NULL = Unexecuted
Comment Text User defined comment.

Additionally, this comment is used for incremental fact load information. Version numbers of the rows loaded are added to the beginning of the comment.

General information

OLAP reads through the un-executed jobs. The un-executed job are indicated by a Status value of NULL. The order that the jobs are executed in is described in the "Parallel processing of the job types" topic.

At the start, the value of the Started column is set to the date-time of the start of the job. After completion, the value in the Completed column is set to the date-time of completion and the Status is set to the error condition from the kernel of the server. The value for success is 0.

The rows from this table are not deleted by the server.

To delete the cube rules, send an empty rules tag. For example:

<Alea:Rules xmlns:Alea="http://www.misag.com" />

If one job fails during the load of the metadata or the execution of the job:

  • The job receives an appropriate error code describing the failure. For example, the connection cannot be established, the metadata is incorrect, or the element does not exist.
  • All other jobs are executed. The failure of one job has no effect on other jobs.
Related topics