Docs/Error messages/Cannot be used with STANDARD edition
Error messagesPermissions

Cannot be used with STANDARD edition

A Standard reservation refuses a table that has a policy tag, a masking rule or a row access policy, and refuses BigQuery ML and search indexes. The four messages, what they mean and where to run the query instead.

BigQuery column-level access control and data masking cannot be used with STANDARD Edition. The following tables are protected by column tags: mydataset.customers. Please see http://cloud.google.com/bigquery/docs/editions-intro for more information.

What BigQuery means

The query runs on a reservation of the Standard edition, and a table it reads has a policy tag or a masking rule. Standard does not support them, so BigQuery refuses the table as a whole. It makes no difference which columns the query reads, whether the table comes in through a view or a join, or whether you hold a Fine-Grained Reader grant.

A dry run gets HTTP 412 with the reason conditionNotMet. A job that was started anyway fails with the reason unknown, so the reason does not tell this error from others and the message does.

The four messages

MessageCause
BigQuery column-level access control and data masking cannot be used with STANDARD Edition. The following tables are protected by column tags: DATASET.TABLE.a table with a policy tag or a masking rule
Using row-level security related functionality is supported in Enterprise edition and above but you are in STANDARD edition. The following tables have row access policies: DATASET.TABLE.a table with a row access policy
Using BQML related functionalities is disallowed in STANDARD edition.CREATE MODEL and other BigQuery ML
SEARCH_INDEX CREATE or DROP DDL is disallowed in STANDARD edition.CREATE SEARCH INDEX and DROP SEARCH INDEX

BigQuery’s row policy message has a space inside its link (editions- intro) and may wrap across lines. Match on the first sentence.

What to do

Run the query on a reservation of the Enterprise edition or above, or on-demand, which has no edition. See reservations for how a query picks one. The refusal is per table, so a query that reads only other tables is not affected.

Leaving a column out does not help. For a refusal by a policy tag on a user without access to it, see Access Denied: neither fine-grained reader nor masked get permission.

In Querylab.io

The editor marks the table in the query that the message names. The message says which tables, and that they cannot be read on a Standard reservation.