Replicate a Cortex Search Service¶

Cortex supports the replication of Cortex Search Services from a source account to one or more target accounts in the same organization. This replication is integrated seamlessly with Snowflake replication and failover groups to provide point-in-time consistency for the objects on the target account. For more information about replication and failover, see Introduction to replication and failover across multiple accounts.

A search service is automatically replicated if the parent database is in a replication or failover group. The following behaviors apply to all replicated Cortex Search Services:

A replicated Cortex Search Service is read only. No direct ALTER or DROP commands are allowed on the replicated entity.
A replicated Cortex Search Service syncs with the primary service according to the replication schedule. Specifically, if the primary replica drops the service, the secondary service is also dropped during replication refresh.
Replication related costs might incur for data transfer and compute resources during replication. There are no additional costs for Cortex Search indexing. For more information, see Understanding replication cost.
The serving status, queryability, and serving billing of a replicated Cortex Search Service differ between replication groups and failover groups:


	Replication group	Failover group
Serving status	Inherits the serving status of the source service. If the source service is active, the replicated service is also active.	Always suspended until the failover group is promoted to primary.
Queryability	Queryable after a delay of up to 10 minutes following replication completion.	Not queryable until promoted to primary.
Serving costs	Billed for serving costs if the source service is in active serving status.	No serving costs until promoted to primary.

For more information about replication and failover groups, see CREATE REPLICATION GROUP.

Create a replicated Cortex Search Service using a replication group¶

To create a replicated Cortex Search Service, create a replication group that includes the parent database of the service.

Create a replication group in the primary account.

CREATE REPLICATION GROUP myrg
    OBJECT_TYPES = DATABASES
    ALLOWED_DATABASES = <database1>
    ALLOWED_ACCOUNTS = <org-name>.<secondary-account>
    REPLICATION_SCHEDULE = '60 MINUTE';

From the secondary account, run the following command to create a replica of the primary account database in the secondary account.
CREATE REPLICATION GROUP myrg AS REPLICA OF <org-name>.<primary-account>.myrg;
From the secondary account, manually refresh the replica.
ALTER REPLICATION GROUP myrg REFRESH;
Create a Cortex Search Service in the primary database. For more information, see CREATE CORTEX SEARCH SERVICE. The search service is automatically replicated according to the replication schedule.

Create a replicated Cortex Search Service using a failover group¶

Failover groups allow you to back up your data in an additional account without using or paying for the replicated services. With a failover group, you can activate the failover only when needed to resume operations. To create a failover group for the Cortex Search Service, create a failover group that includes the parent database of the service.

Create a failover group in the primary account.

CREATE FAILOVER GROUP myrg
    OBJECT_TYPES = DATABASES
    ALLOWED_DATABASES = <database1>
    ALLOWED_ACCOUNTS = <org-name>.<secondary-account>
    REPLICATION_SCHEDULE = '60 MINUTE';

From the secondary account, run the following command to create a failover of the primary account database in the secondary account.
CREATE FAILOVER GROUP myrg AS REPLICA OF <org-name>.<primary-account>.myrg;
From the secondary account, manually refresh the failover group.
ALTER FAILOVER GROUP myrg REFRESH;
Create a Cortex Search Service in the primary database. For more information, see CREATE CORTEX SEARCH SERVICE. The search service is automatically replicated according to the replication schedule.
At the time of disaster recovery, run the following sql in the secondary account to make it the new primary. The replicated service will be activated and loaded into the serving system to query.
ALTER FAILOVER GROUP myrg PRIMARY;