> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/reference-1/monitoring/job-status/cdc-sources/job-settings.md).

# Job Settings

The **Job Settings** tab displays the SQL code used to create the job, alongside job options, and details:

<figure><img src="/files/nGHmWV0LhS0VojpNegrA" alt=""><figcaption><p>The Job Settings tab shows the SQL code to create the job, along with job options, and details</p></figcaption></figure>

## SQL

View the full SQL code used to generate the job. This code includes all job and source options provided when you created the job, or the default options used by Upsolver.  &#x20;

The code can be copied into a Worksheet if you want to re-use it.

***

## Options

The job options provided when you created the job or the default options used by Upsolver - these will vary depending on your source database:

<table><thead><tr><th width="263">Job Option</th><th>Value</th></tr></thead><tbody><tr><td>COMPUTE_CLUSTER</td><td><p>The name of the cluster that executes the job. </p><p>Click on the link to <a href="/pages/EwzZMOK981z0SRDPiKMz">view further details</a> about the cluster.</p></td></tr><tr><td>HEARTBEAT_TABLE</td><td>The name of the heartbeat table for PostgreSQL sources.</td></tr><tr><td>INTERMEDIATE_STORAGE_CONNECTION</td><td>The name of the connection to stage the data ingested from the CDC source.</td></tr><tr><td>PUBLICATION_NAME</td><td>The publication name for PostgreSQL sources.</td></tr><tr><td>PARSE_JSON_COLUMNS</td><td>If <strong>true</strong>, Upsolver will parse JSON columns into a struct matching the JSON value.</td></tr><tr><td>SKIP_SNAPSHOTS</td><td>When <strong>true</strong>, Upsolver will not take an initial snapshot and only process change events starting from the time the ingestion job is created. Otherwise, a snapshot will be taken.</td></tr><tr><td>MERGE_PARTITIONED_TABLES</td><td>If <strong>true</strong>, Upsolver will merge the partitioned tables.</td></tr><tr><td>INTERMEDIATE_STORAGE_LOCATION</td><td>The name of the location to stage the data ingested from the CDC source.</td></tr></tbody></table>

## Details

The following details about your job are displayed:

<table><thead><tr><th width="182">Detail</th><th>Value</th></tr></thead><tbody><tr><td>Description</td><td>The optional comment provided when the job was created or updated. </td></tr><tr><td>Created At</td><td>The date and time when the job was initially created.</td></tr><tr><td>Last Modified At</td><td>The date and time when the job was last updated.</td></tr><tr><td>Created By</td><td>The username of the person in your organization who created the job.</td></tr><tr><td>Last Modified By</td><td>The username of the last person in your organization to update the job.</td></tr><tr><td>Id</td><td><p>The globally unique identifier for the job. </p><p>This Id can be used when querying <a href="/pages/zP43rtCKylqFv0ktIHtK">system.information_schema.jobs</a> and the <a href="/pages/NmVM3rZUQQeygomOBNnd">system.monitoring.jobs</a> tables.</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://upsolver.gitbook.io/content/reference-1/monitoring/job-status/cdc-sources/job-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
