DOCSP-45120-change-sync-to-migration (#180)

* DOCSP-45120-change-sync-to-migration

* DOCSP-45120 removing constants

* DOCSP-45120 tech edit

* DOCSP-45120 fixing build

Author: ltran-mdb2

snooty.toml

@@ -46,8 +46,6 @@ toc_landing_pages = [
 [constants]
 connector-version = "2.7.0"
 ddl = ":abbr:`DDL (Data Definition Language)`"
-job = "sync job" #this will be updated to migration job in the near future.
-job_plural = "sync jobs" #this will be updated to migration jobs in the near future.
 migrator-api = "REST API Documentation"
 migrator-api-endpoints = "Endpoints"
 

source/api-docs.txt

@@ -21,7 +21,7 @@ Relational Migrator REST API
 The Relational Migrator REST API provides you with programmatic access 
 to Relation Migrator with HTTPS endpoints. The REST API is a 
 Relational Migrator service between your application and your source and 
-destination databases that you can send requests to manage your sync jobs.
+destination databases that you can send requests to manage your migration jobs.
 
 You don't need to install any additional extensions or packages to use 
 the Relational Migrator REST API. The functionality is part of the 
@@ -59,7 +59,7 @@ Use the Relational Migrator REST API when:
   ``WHERE DATEDIFF(CURDATE(), last_modified) <= 1`` to batch migrate 
   data on a cadence from your relational database to MongoDB. 
 
-- You want to programmatically create Relational Migrator sync jobs 
+- You want to programmatically create Relational Migrator migration jobs 
   dynamically. For example, using connection strings from 
   multiple databases without manually configuring them in the GUI.
 

source/code-generation/query-converter/test-converted-queries/compare-converted-queries.txt

@@ -14,7 +14,7 @@ You can use the :guilabel:`Test Queries` pane to compare source
 and destination queries, views, and stored procedure results 
 in Relational Migrator. The :guilabel:`Test Queries` can 
 help you verify the accuracy of converted code and
-show the source and destination data after you run a sync job.
+show the source and destination data after you run a migration job.
 
 About this Task
 ---------------

source/connection-strings/connection-strings.txt

@@ -14,7 +14,7 @@ Relational Migrator uses connection strings to connect to both
 the relational and MongoDB databases. You can create connection strings:
 
 - Using the UI when you create a project.
-- Using the UI when you create a sync job.
+- Using the UI when you create a migration job.
 - By manually providing the Uniform Resource Identifier (URI).
 
 Get Started

source/connection-strings/mongodb-database-connection-strings.txt

@@ -137,4 +137,4 @@ Results
 -------
 
 The MongoDB connection URI is optionally specified as part of the process for
-creating a Relational Migrator project or when creating a sync job.
+creating a Relational Migrator project or when creating a migration job.

source/getting-started.txt

@@ -20,7 +20,7 @@ Get Started with Relational Migrator
 
 Relational Migrator is a tool to help you migrate your relational 
 data to MongoDB. This page guides you through installing the tool 
-and running your first sync job.
+and running your first migration job.
 
 To get familiar with Relational Migrator capabilities, 
 features, and use cases, review the following resources:
@@ -64,16 +64,16 @@ Steps
       the destination data model that best matches your 
       application needs.
 
-   .. step:: Create a sync job
+   .. step:: Create a migration job
 
-      :ref:`Sync jobs <rm-sync-jobs>` move the data from relational 
-      tables to MongoDB collections. Sync jobs have two types: 
+      :ref:`Migration jobs <rm-sync-jobs>` move the data from relational 
+      tables to MongoDB collections. Migration jobs have two types: 
 
       - **Snapshot** for point in time migrations. 
       - **Continuous** for ongoing change data capture zero-downtime migrations.
 
       To start your migration to MongoDB, 
-      :ref:`create a sync job <rm-create-jobs>`.
+      :ref:`create a migration job <rm-create-jobs>`.
 
 .. toctree::
    :titlesonly:

source/getting-started/atlas-log-in.txt

@@ -13,7 +13,7 @@ Log In with Atlas
 You can optionally sign in to your Atlas account inside Relational 
 Migrator. If you log in, you can access the 
 :ref:`Query Converter <rm-query-converter>` feature and you can choose 
-destination clusters from a list when creating sync jobs.
+destination clusters from a list when creating migration jobs.
 
 Before you Begin
 ----------------

source/getting-started/migration-scenarios.txt

@@ -49,7 +49,7 @@ destination databases remain in sync.
 After the continuous sync migration completes, you can transfer users to
 the new application and shut down the legacy application.
 
-To learn more about sync jobs, see :ref:`rm-sync-jobs`.
+To learn more about migration jobs, see :ref:`rm-sync-jobs`.
 
 Currently Unsupported Migration Scenarios
 -----------------------------------------

source/includes/fact-calculated-fields-type.rst

@@ -1,3 +1,3 @@
 When defining :ref:`rm-calculated-fields` and :ref:`rm-id-field-customizations`, 
 Relational Migrator shows an initial data type of :guilabel:`default`. 
-When you run a sync job, Relational Migrator updates this data type.
+When you run a migration job, Relational Migrator updates this data type.

source/includes/fact-cdc-recoverable.rst

@@ -1,2 +1,2 @@
-You can recover a continuous sync job within 24 hours of failure. 
+You can recover a continuous migration job within 24 hours of failure. 
 For details, see :ref:`rm-sync-jobs-recoverability`.

source/includes/fact-data-prep-oracle-step1.rst

@@ -14,7 +14,7 @@ a. Create a service account:
 #. Grant select permissions to the service account:
 
    The required permission for the service account depend on whether 
-   the tables are owned by the service account used to run the sync job.
+   the tables are owned by the service account used to run the migration job.
    To check table ownership run the following query:
 
    .. code-block:: sql

source/includes/fact-kafka-additional-time.rst

@@ -1,4 +1,4 @@
-- Continuous sync jobs using Confluent Cloud Kafka may take additional 
+- Continuous migration jobs using Confluent Cloud Kafka may take additional 
   time due to the provisioning of backend resources on Confluent Cloud.
   This process typically takes an additional two to five 
-  minutes the first time a CDC sync job runs.
+  minutes the first time a CDC migration job runs.

source/includes/fact-kafka-supported-task.rst

@@ -1,3 +1,3 @@
 This task also applies to Apache Kafka supported 
-continuous sync jobs. There is no procedural difference introduced when 
+continuous migration jobs. There is no procedural difference introduced when 
 using Kafka. For more details, see :ref:`kafka-intro`.

source/includes/fact-mapping-options-configure-fields.rst

@@ -15,5 +15,5 @@ a. Define the options for the new mapping rule. When defining the
 
    - Change field names.
 
-   - Include or exclude a field from your sync job by clicking the
+   - Include or exclude a field from your migration job by clicking the
      :icon-fa5:`check-square` icon next to the field name.

source/includes/fact-short-sync-job-desc.rst

@@ -1,3 +1,3 @@
-- Snapshot sync jobs migrate all the data and then stops.
-- Continuous sync job run a snapshot and then enter a CDC stage to 
+- Snapshot migration jobs migrate all the data and then stops.
+- Continuous migration job run a snapshot and then enter a CDC stage to 
   continuously replicate data changes.

source/index.txt

@@ -150,7 +150,7 @@ Explore libraries and tools for MongoDB.
    Mapping Rules </mapping-rules/mapping-rules>
    Table Filters </table-filters/table-filters>
    Diagrams </diagrams/diagrams>
-   Sync Jobs </jobs/sync-jobs>
+   Migration Jobs </jobs/sync-jobs>
    Connection Strings </connection-strings/connection-strings>
    Code Generation </code-generation>
    {+migrator-api+} <api-docs>

source/installation.txt

@@ -44,7 +44,7 @@ For instructions on installing Relational Migrator, see the following pages:
    * - Kafka
 
      - The Kafka deployment method is suitable for long-running Change Data 
-       Capture (CDC) sync jobs and large data migrations that exceed 4 weeks in 
+       Capture (CDC) migration jobs and large data migrations that exceed 4 weeks in 
        duration or involve databases larger than 20GB. `Apache Kafka 
        <https://kafka.apache.org/>`__ is an open-source platform for distributed 
        workloads that offers high availability and automatic recovery. This is the 

source/installation/deployment-considerations.txt

@@ -58,7 +58,7 @@ the most:
 .. tip::
 
    Check the sleep timeout setting for your operating system. If your 
-   machine goes to sleep during a migration, the sync job fails. 
+   machine goes to sleep during a migration, the migration job fails. 
 
 Network Considerations
 ----------------------

source/installation/kafka-deployments/migrator-with-kafka.txt

@@ -26,7 +26,7 @@ Use Cases
 ---------
 
 Relational Migrator with Kafka is intended for large and long running jobs.
-Kafka's built-in resilience ensures the sync job can recover and continue 
+Kafka's built-in resilience ensures the migration job can recover and continue 
 running if any component becomes temporarily unavailable. 
 
 Behavior

source/installation/system-requirements.txt

@@ -75,7 +75,7 @@ web browsers:
 Kafka Deployments
 -----------------
 
-You can optionally use Kafka for long-running sync jobs. For details.
+You can optionally use Kafka for long-running migration jobs. For details.
 see :ref:`kafka-intro`.
 
 Supported Databases

source/jobs/creating-jobs.txt

@@ -1,25 +1,25 @@
 .. _rm-create-jobs:
 
-=================
-Create a Sync Job
-=================
+======================
+Create a Migration Job
+======================
 
 .. contents:: On this page
    :local:
    :backlinks: none
    :depth: 1
    :class: singlecol
 
-Sync jobs are the worker processes responsible for transferring your 
+Migration jobs are the worker processes responsible for transferring your 
 data and schemas from a relational database to MongoDB. Create a new 
-sync job from the :guilabel:`Data Migration` tab.
+migration job from the :guilabel:`Data Migration` tab.
 
 .. include:: /includes/fact-kafka-supported-task.rst
 
 About this Task
 ---------------
 
-- The URI credentials you provide when creating a sync job do not 
+- The URI credentials you provide when creating a migration job do not 
   need to be the same as the credentials used when creating your project.
 
 .. include:: /includes/fact-kafka-additional-time.rst
@@ -39,10 +39,10 @@ Steps
 
 .. procedure::
 
-  .. step:: Click the :guilabel:`Create Sync Job` button
+  .. step:: Click the :guilabel:`Create Migration Job` button
 
-    On the :guilabel:`Data Migration` tab, click :guilabel:`Create Sync Job`. 
-    Relational Migrator only runs one sync job at a time. If a sync job is in 
+    On the :guilabel:`Data Migration` tab, click :guilabel:`Create Migration Job`. 
+    Relational Migrator only runs one migration job at a time. If a migration job is in 
     progress, this button is disabled.
 
   .. step:: Enter the relational database connection details
@@ -148,13 +148,13 @@ Steps
         * - Migration Option
           - Description
         * - Mode 
-          - Defines the type of sync job.
+          - Defines the type of migration job.
         * - Drop destination collections before migration
           - Boolean. Indicates whether Relational Migrator drops a 
             destination collection before transferring data. 
         * - Stop after errors 
           - Integer. Indicates the number of errors after which Relational 
-            Migrator stops the sync job.  
+            Migrator stops the migration job.  
         * - Verify migrated data 
           - Boolean. If true, the sync engine checks the migrated data 
             against the source database. Only supported for snapshot mode.
@@ -171,23 +171,23 @@ Steps
 
       .. warning:: 
 
-        Before proceeding with starting a sync job:
+        Before proceeding with starting a migration job:
 
         1. Download the script. 
         2. Carefully review its contents.
         3. Execute the statements.
         4. Follow any commented manual steps.
 
-  .. step:: Review and start your sync job
+  .. step:: Review and start your migration job
 
       On the :guilabel:`Review Summary` form, you can see details about 
-      your sync job. These details include the type, the number of 
+      your migration job. These details include the type, the number of 
       tables and rows affected, and the estimated data size of the 
-      sync job. To start your sync job, click :guilabel:`Start`. 
+      migration job. To start your migration job, click :guilabel:`Start`. 
 
       .. note :: 
 
-         For Kafka sync jobs, view deployment details by selecting the 
+         For Kafka migration jobs, view deployment details by selecting the 
          job in the :guilabel:`History` pane on the 
          :guilabel:`Data Migration` screen and hovering
          over the icon next to the :guilabel:`Create Migration Job`

source/jobs/data-verification/data-verification.txt

@@ -12,13 +12,13 @@ Data Verification
 
 Data verification is a process that is built into the sync engine.
 The data verification process uses the source and destination 
-connection strings to validate that a sync job was successful.
+connection strings to validate that a migration job was successful.
 
-- Data verification is supported for one-time sync jobs.
-- By default, data verification is not performed when running a sync job. 
+- Data verification is supported for one-time migration jobs.
+- By default, data verification is not performed when running a migration job. 
   You must explicitly opt-in to verification in :guilabel:`Migration Options` 
   before the job is started.
-- Enabling data verification can add significant compute time to a sync 
+- Enabling data verification can add significant compute time to a migration 
   job.
 
 When data verification is successful, source and destination states match.

source/jobs/data-verification/use-data-verification.txt

@@ -11,26 +11,26 @@ Use Data Verification
    :class: singlecol
 
 Data verification optionally runs as a separate process that is tightly
-coupled to a sync job. Data verification can be enabled for one-time 
-sync jobs. This page details how to enable and debug the 
+coupled to a migration job. Data verification can be enabled for one-time 
+migration jobs. This page details how to enable and debug the 
 data verification process.
 
 Enable Data Verification
 ------------------------
 
 You can optionally enable data verification when 
-:ref:`creating a sync job <rm-create-jobs>` on the :guilabel:`Data Migration` tab.
+:ref:`creating a migration job <rm-create-jobs>` on the :guilabel:`Data Migration` tab.
 
 On the :guilabel:`Migration Options` module, click the 
-:guilabel:`Verify migrated data` check box for your sync job.
+:guilabel:`Verify migrated data` check box for your migration job.
 
 .. note::
 
-   The Data Verification process can take as long or longer than the data sync job.
+   The Data Verification process can take as long or longer than the data migration job.
    You can click :guilabel:`Terminate` to cancel a Data Verification process.
 
 To view status and metadata information about the data verification process
-for a sync job, click the :guilabel:`Data Verification` drop-down menu:
+for a migration job, click the :guilabel:`Data Verification` drop-down menu:
 
 .. image:: /img/jobs/data-verification/data-verification-click-dropdown.png
    :alt: Click Data Verification Drop-Down
@@ -39,7 +39,7 @@ Data Verification Overview
 --------------------------
 
 On the :guilabel:`Data Verification` pane, you can view the metadata 
-about a sync jobs verification process.
+about a migration jobs verification process.
 
 .. list-table::
    :header-rows: 1
@@ -87,7 +87,7 @@ A data verification process can be any of the following statuses:
 Successful Data Verification
 ----------------------------
 
-When a sync job is successful the status updates to :guilabel:`Verified`
+When a migration job is successful the status updates to :guilabel:`Verified`
 and a double checkmark is displayed in the :guilabel:`History` pane:
 
 .. image:: /img/jobs/data-verification/data-verification-double-checkmark.png