> 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/sql-commands/jobs.md).

# Jobs

Jobs enable you to ingest and transform your data. They can read from external sources and write data into a table, or read from a table and write to another table or an external target.

In Upsolver, there are three types of data movement jobs: **ingestion**, **replication**, and **transformation**. Each of these jobs may be created as either synchronized or non-synchronized jobs. You can also create a **monitoring** job to export job metrics to a third-party monitoring platform.

1. [Ingestion](/content/reference-1/sql-commands/jobs/create-job/ingestion.md) jobs copy from a supported source and insert the raw data into a staging table in your Amazon S3-based data lake, or directly ingest the data into supported targets. These jobs automatically detect and infer the schema and, when writing to data lake tables, update the AWS Glue Data Catalog with column names, types, and partition information. Furthermore, you can apply transformations if your data requires alteration prior to loading into your target.&#x20;
2. [Replication](/content/reference-1/sql-commands/jobs/create-job/replication.md) jobs copy change data capture (CDC) from enabled databases into one or more target schemas in Snowflake. Sharing a single data source, multiple replication groups can be individually configured to write to multiple schemas using different intervals and options.
3. [Transformation](/content/reference-1/sql-commands/jobs/create-job/transformation.md) jobs insert and merge data into tables in your data lake, data warehouse, and other targets. You can transform, model, join, and aggregate data before inserting the results into the target system. Using a primary key, transformation jobs can insert, update, and delete rows automatically.
4. [Monitoring](/content/reference-1/sql-commands/jobs/create-job/monitoring.md) jobs enable you to stream job metrics to Amazon CloudWatch and Datadog, enabling you to monitor your pipeline jobs from a centralized dashboard.

{% hint style="info" %}
Before creating a job, it is important to understand the difference between synchronized and non-synchronized jobs.&#x20;

Please read the article [Understanding Sync and Non-Sync Jobs](/content/articles-1/get-started/understanding-sync-and-non-sync-jobs.md).
{% endhint %}


---

# 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/sql-commands/jobs.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.
