Listing sharded property databases
Enterprise EditionNot available on AuraIntroduced in 2025.12

Sharded databases are listed as standard databases in the type column when you execute SHOW DATABASES. See List databases for more information.

  • The status is either:

    • Equal to the status shared by all shards.

    • “Mixed”, if some shards have a different status. The statusMessage indicates the number of shards with different statuses, e.g., online (4) and starting (1).

  • The associated graph shard is listed as graph shard in the type column.

  • The associated property shards are listed as property shard in the type column.

  • The shardTxnLag column displays the number of transactions the current shard is behind compared to the most up-to-date shard allocation of the sharded database. The lag is expressed in negative integers.

  • The column replicationLag shows the number of transactions the current database is behind compared to the most up-to-date allocation of that database.

Command output
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| name       | type             | aliases | access       | address          | role                     | writer | requestedStatus | statusMessage | default | home  | constituents | shardTxnLag |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| "foo"      | "standard"       | []      | "read-write" | "localhost:7687" | "primary"                | TRUE   | "online"        | ""            | FALSE   | FALSE | []           | NULL        |
| "foo-g000" | "graph shard"    | []      | "read-write" | "localhost:7687" | "primary"                | TRUE   | "online"        | ""            | FALSE   | FALSE | []           | 0           |
| "foo-p000" | "property shard" | []      | "read-write" | "localhost:7687" | "property shard replica" | FALSE  | "online"        | ""            | FALSE   | FALSE | []           | 0           |
| "foo-p001" | "property shard" | []      | "read-write" | "localhost:7687" | "property shard replica" | FALSE  | "online"        | ""            | FALSE   | FALSE | []           | 0           |
| "foo-p002" | "property shard" | []      | "read-write" | "localhost:7687" | "property shard replica" | FALSE  | "online"        | ""            | FALSE   | FALSE | []           | 0           |
| "system"   | "system"         | []      | "read-write" | "localhost:7687" | "primary"                | TRUE   | "online"        | ""            | FALSE   | FALSE | []           | NULL        |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Some columns are empty for the virtual sharded database (with the name passed into the CREATE DATABASE command) and can be found on the rows of the associated graph shard instead, e.g., lastCommittedTxn or replicationLag. These rows are only visible if the user has either CREATE/DROP/ALTER DATABASE, SET DATABASE ACCESS, or DATABASE MANAGEMENT privileges. These rows can be distinguished by the type, which has values graph shard and property shard, respectively.