# \_SYNC\_PLANS

Synchronizes a node's local PPC with the DPC for a specific database.

```sql
_SYNC_PLANS <dbName>;
```

When this command is run on a node, it downloads up to `distributed_plancache_max_download_plans` from the DPC to that node's local PPC for the specified database.

The `_SYNC_PLANS` command first downloads one plan per table in the database. Query plans are downloaded only after these "table plans" are downloaded. For databases in which the number of tables in the database is close to the value of `distributed_plancache_max_download_plans`, SingleStore recommends increasing the value of `distributed_plancache_max_download_plans` to a value greater than the number of tables in the database before running the command.

When the `_SYNC_PLANS` command is run, a synchronization task will be added to the DPC task queue regardless of whether enable\_distributed\_plancache is set to `ON` or `OFF`. If the request is enqueued while enable\_distributed\_plancache is set to `OFF`, the task will run when enable\_distributed\_plancache is set to `ON`.

Refer to [Distributed Plancache](https://docs.singlestore.com/cloud/user-and-workspace-administration/workspace-health-and-performance/distributed-plancache.md) for more information.

***

Modified at: May 29, 2026

Source: [/cloud/reference/sql-reference/code-generation-functions/sync-plans/](https://docs.singlestore.com/cloud/reference/sql-reference/code-generation-functions/sync-plans/)

(An index of the documentation is available at /llms.txt)