Categories:

Table, View, & Sequence DDL

# SHOW PRIMARY KEYS¶

Lists primary keys for the specified table, or for all tables in the current or specified schema, or for all tables in the current or specified database, or for all tables in the current account.

## Syntax¶

SHOW [ TERSE ] PRIMARY KEYS
[ IN { ACCOUNT | DATABASE [ <database_name> ] | SCHEMA [ <schema_name> ] | TABLE | [ TABLE ] <table_name> } ]


## Parameters¶

TERSE

This clause is accepted syntactically but has no effect on the output.

IN { ACCOUNT | DATABASE [ <database_name> ] | SCHEMA [ <schema_name> ] | TABLE | [ TABLE ] <table_name> }

Specifies the scope of the command, which determines whether the command lists records only for the current or specified database, schema, table, or account.

If you specify the keyword ACCOUNT, then the command retrieves records for all schemas in all databases of the current account.

If you specify the keyword DATABASE, then:

• If you specify a <database_name>, then the command retrieves records for all schemas of the specified database.

• If you do not specify a <database_name>, then:

• If there is a current database, then the command retrieves records for all schemas in the current database.

• If there is no current database, then the command retrieves records for all databases and schemas in the account.

If you specify the keyword SCHEMA, then:

• If you specify a qualified schema name (e.g. my_database.my_schema), then the command retrieves records for the specified database and schema.

• If you specify an unqualified <schema_name>, then:

• If there is a current database, then the command retrieves records for the specified schema in the current database.

• If there is no current database, then the command displays the error SQL compilation error: Object does not exist, or operation cannot be performed.

• If you do not specify a <schema_name>, then:

• If there is a current database, then:

• If there is a current schema, then the command retrieves records for the current schema in the current database.

• If there is no current schema, then the command retrieves records for all schemas in the current database.

• If there is no current database, then the command retrieves records for all databases and all schemas in the account.

If you specify the keyword TABLE without a table_name, then:

• If there is a current database, then:

• If there is a current schema, then the command retrieves records for the current schema in the current database.

• If there is no current schema, then the command retrieves records for all schemas in the current database.

• If there is no current database, then the command retrieves records for all databases and all schemas in the account.

If you specify a <table_name> (with or without the keyword TABLE), then:

• If you specify a fully-qualified <table_name> (e.g. my_database_name.my_schema_name.my_table_name), then the command retrieves all records for the specified table.

• If you specify a schema-qualified <table_name> (e.g. my_schema_name.my_table_name), then:

• If a current database exists, then the command retrieves all records for the specified table.

• If no current database exists, then the command displays an error similar to Cannot perform SHOW <object_type>. This session does not have a current database....

• If you specify an unqualified <table_name>, then:

• If a current database and current schema exist, then the command retrieves records for the specified table in the current schema of the current database.

• If no current database exists or no current schema exists, then the command displays an error similar to: SQL compilation error: <object> does not exist or not authorized..

Default: Depends on whether the session currently has a database in use:

• Database: DATABASE is the default (i.e. the command returns the objects you have privileges to view in the database).

• No database: ACCOUNT is the default (i.e. the command returns the objects you have privileges to view in your account).

## Usage Notes¶

• The command does not require a running warehouse to execute.

• For each single-column primary key, the output contains one row.

• For each multi-column primary key, the output contains one row for each column in the primary key.

• If an account (or database or schema) has a large number of tables, then searching the entire account (or table or schema) can consume a significant amount of compute resources.

• To post-process the output of this command, you can use the RESULT_SCAN function, which treats the output as a table that can be queried.

Important

Remember that Snowflake treats primary key constraints as NOT NULL constraints. Snowflake does not enforce unique values for primary keys.

## Output¶

The command output provides primary key properties and metadata in the following columns:

The command output provides primary key properties and metadata in the following columns:

| created_on | database_name | schema_name | table_name | column_name | key_sequence | comment | constraint_name |


Column

Description

created_on

Date and time when the table was created.

database_name

Database in which the table is stored.

schema_name

Schema in which the table is stored.

table_name

Name of the table.

column_name

Name of the column in the primary key.

key_sequence

If the primary key is composed of multiple columns, then the number in the key_sequence column indicates the order of those columns in the primary key. For example, if the primary key is defined as CONSTRAINT pkey1 PRIMARY KEY (column_x, column_y), then the key_sequence number for column_x is 1 and the key_sequence number for column_y is 2.

comment

The comment (if any) specified for the constraint when the constraint was created.

constraint_name

The name of the constraint.

## Examples¶

show primary keys;

show primary keys in account;

show primary keys in database;

show primary keys in database my_database;

show primary keys in schema;

show primary keys in schema my_schema;

show primary keys in schema my_database.my_schema;

show primary keys in my_table;

show primary keys in my_database.my_schema.my_table;