Database Ingestion and Replication > Managing database ingestion and replication jobs > Stopping a database ingestion and replication job
  

Stopping a database ingestion and replication job

You can stop a database ingestion and replication job of any load type that is in the Up and Running, Running with Warning, or On Hold state.
For an incremental load job, the job stops after a checkpoint is taken. A checkpoint records the point in the change stream where incremental processing left off for recovery purposes.
For a combined initial and incremental load job, initial load subtasks that are running are allowed to run to completion and Initial load subtasks that are not running remain in their current states. For the incremental load portion of the job, a checkpoint is written to the checkpoint file or target recovery table before the job stops. The database ingestion and replication job will not be able to record a checkpoint unless a change record has been processed for at least one of the tables in the job during the first job run after deployment. If a checkpoint is not available, the job resumes processing from the configured restart point, which is the latest available position in the change stream by default.
For an initial load job, any running subtasks are allowed to run to completion and then the job stops. Non-running subtasks remain in their current states.
Note: Before stopping a database ingestion and replication incremental load or combined load job that has a Snowflake target and uses the Superpipe option, ensure that all ingested data in the change stream has been merged into the target. Otherwise, if the job is not restarted for an extended period or before the stream expires, any data that remains in the stream is lost and can’t be recovered.
    1Navigate to the row for the job that you want to stop in any of the following monitoring interfaces:
    2In the Actions menu for the row, select Stop, or click the Stop icon next to the menu.
    The job state switches to Stopping and then to Stopped.
    Tip: If the Stop operation is taking too long, you can abort the job.