†*BY_PROJECT 뷰의 경우 BY_PROJECT 서픽스가 선택사항입니다. 예를 들어 INFORMATION_SCHEMA.JOBS_BY_PROJECT 및 INFORMATION_SCHEMA.JOBS를 쿼리해도 동일한 결과가 반환됩니다.
가격 책정
주문형 가격을 사용하는 프로젝트의 경우 INFORMATION_SCHEMA 뷰에 대한 쿼리는 쿼리로 처리되는 바이트 수가 10MB 미만이더라도 최소 10MB의 데이터 처리 비용을 청구합니다. 주문형 쿼리의 최소 청구 금액은 10MB입니다. 자세한 내용은 주문형 가격 책정을 참조하세요.
용량 기반 가격 책정을 사용하는 프로젝트의 경우 INFORMATION_SCHEMA 뷰와 테이블에 대한 쿼리는 구매한 BigQuery 슬롯을 사용합니다. 자세한 내용은 용량 기반 가격 책정을 참조하세요.
INFORMATION_SCHEMA 쿼리는 캐시되지 않으므로 쿼리 텍스트가 동일해도 INFORMATION_SCHEMA 쿼리를 실행할 때마다 요금이 청구됩니다.
INFORMATION_SCHEMA 뷰에 대한 스토리지 수수료는 청구되지 않습니다.
구문
INFORMATION_SCHEMA 뷰는 데이터 세트 또는 리전으로 한정되어야 합니다.
데이터 세트 한정자
데이터 세트 한정자가 있으면 지정된 데이터 세트로 결과가 제한됩니다.
예를 들면 다음과 같습니다.
-- Returns metadata for tables in a single dataset.SELECT*FROMmyDataset.INFORMATION_SCHEMA.TABLES;
다음 INFORMATION_SCHEMA 뷰는 데이터 세트 한정자를 지원합니다.
COLUMNS
COLUMN_FIELD_PATHS
MATERIALIZED_VIEWS
PARAMETERS
PARTITIONS
ROUTINES
ROUTINE_OPTIONS
TABLES
TABLE_OPTIONS
VIEWS
리전 한정자
리전 한정자는 region-REGION 구문을 사용하여 표현됩니다.
모든 데이터 세트 위치 이름을 REGION에 사용할 수 있습니다. 예를 들어 다음 리전 한정자는 유효합니다.
region-us
region-asia-east2
region-europe-north1
리전 한정자가 있으면 지정된 위치로 결과가 제한됩니다. 예를 들어 다음 쿼리는 US 멀티 리전에서 프로젝트에 있는 모든 데이터 세트에 대해 메타데이터를 반환합니다.
-- Returns metadata for all datasets in a region.SELECT*FROMregion-us.INFORMATION_SCHEMA.SCHEMATA;
리전이 한정된 INFORMATION_SCHEMA 뷰에 대한 쿼리는 지정된 리전에서 실행되므로 단일 쿼리를 작성하여 서로 다른 리전의 뷰에서 데이터를 조인할 수 없습니다. 여러 리전의 INFORMATION_SCHEMA 뷰를 결합하려면 쿼리 결과를 로컬에서 읽고 결합하거나 결과 테이블을 공통 리전으로 복사합니다.
프로젝트 한정자
프로젝트 한정자가 있으면 지정된 프로젝트로 결과가 제한됩니다.
예를 들면 다음과 같습니다.
-- Returns metadata for the specified project and region.SELECT*FROMmyProject.`region-us`.INFORMATION_SCHEMA.TABLES;-- Returns metadata for the specified project and dataset.SELECT*FROMmyProject.myDataset.INFORMATION_SCHEMA.TABLES;
모든 INFORMATION_SCHEMA 뷰가 프로젝트 한정자를 지원합니다. 프로젝트 한정자를 지정하지 않으면 뷰가 기본적으로 쿼리를 실행 중인 프로젝트로 지정됩니다.
조직 수준의 뷰(예: STREAMING_TIMELINE_BY_ORGANIZATION)에 대한 프로젝트 한정자를 지정해도 결과에 영향을 주지 않습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003e\u003ccode\u003eINFORMATION_SCHEMA\u003c/code\u003e views in BigQuery are read-only, system-defined views that provide metadata about BigQuery objects.\u003c/p\u003e\n"],["\u003cp\u003eThese views support dataset, region, and project qualifiers to restrict results to a specific scope, and if neither a region nor dataset qualifier is specified, an error will occur.\u003c/p\u003e\n"],["\u003cp\u003eQueries against \u003ccode\u003eINFORMATION_SCHEMA\u003c/code\u003e views incur a minimum of 10 MB of data processing charges for on-demand pricing, or consume capacity for projects using capacity-based pricing, and are not cached.\u003c/p\u003e\n"],["\u003cp\u003eThe views do not contain information about hidden datasets, and permissions are checked at the parent level, not at the individual row level.\u003c/p\u003e\n"],["\u003cp\u003eAll \u003ccode\u003eINFORMATION_SCHEMA\u003c/code\u003e views must use GoogleSQL syntax, and they are not supported in legacy SQL, nor in DDL statements.\u003c/p\u003e\n"]]],[],null,["# Introduction to INFORMATION_SCHEMA\n==================================\n\nThe BigQuery `INFORMATION_SCHEMA` views are read-only, system-defined\nviews that provide metadata information about your BigQuery\nobjects. The following table lists all `INFORMATION_SCHEMA` views that you can\nquery to retrieve metadata information:\n\n^†^ For `*BY_PROJECT` views, the `BY_PROJECT` suffix is optional. For\nexample, querying `INFORMATION_SCHEMA.JOBS_BY_PROJECT` and `INFORMATION_SCHEMA.JOBS`\nreturn the same results.\n| **Note:** Not all `INFORMATION_SCHEMA` views are supported for [BigQuery Omni system tables](/bigquery/docs/omni-introduction#limitations). You can view resource metadata with `INFORMATION_SCHEMA` for [Amazon S3](/bigquery/docs/omni-aws-create-external-table#view_resource_metadata) and [Azure Storage](/bigquery/docs/omni-azure-create-external-table#view_resource_metadata_with_information_schema).\n\nPricing\n-------\n\nFor projects that use on-demand pricing, queries against `INFORMATION_SCHEMA`\nviews incur a minimum of 10 MB of data processing charges, even if the bytes\nprocessed by the query are less than 10 MB. 10 MB is the minimum\nbilling amount for on-demand queries. For more information, see\n[On-demand pricing](/bigquery/pricing#on_demand_pricing).\n\nFor projects that use capacity-based pricing, queries against `INFORMATION_SCHEMA`\nviews and tables consume your purchased BigQuery slots. For more\ninformation, see [capacity-based pricing](/bigquery/pricing#capacity_compute_analysis_pricing).\n\nBecause `INFORMATION_SCHEMA` queries are not cached, you are charged each time\nthat you run an `INFORMATION_SCHEMA` query, even if the query text is the same\neach time you run it.\n\nYou are not charged storage fees for the `INFORMATION_SCHEMA` views.\n\nSyntax\n------\n\nAn `INFORMATION_SCHEMA` view needs to be qualified with a dataset or region.\n| **Note:** You must [specify a location](/bigquery/docs/locations#specify_locations) to query an `INFORMATION_SCHEMA` view. Querying an `INFORMATION_SCHEMA` view fails with the following error if the location of the query execution doesn't match the location of the dataset or regional qualifier used: \n|\n| ```\n| Table myproject: region-us.INFORMATION_SCHEMA.[VIEW] not found in location US\n| ```\n\n### Dataset qualifier\n\nWhen present, a dataset qualifier restricts results to the specified dataset.\nFor example: \n\n -- Returns metadata for tables in a single dataset.\n SELECT * FROM myDataset.INFORMATION_SCHEMA.TABLES;\n\nThe following `INFORMATION_SCHEMA` views support dataset qualifiers:\n\n- `COLUMNS`\n- `COLUMN_FIELD_PATHS`\n- `MATERIALIZED_VIEWS`\n- `PARAMETERS`\n- `PARTITIONS`\n- `ROUTINES`\n- `ROUTINE_OPTIONS`\n- `TABLES`\n- `TABLE_OPTIONS`\n- `VIEWS`\n\n### Region qualifier\n\nRegion qualifiers are represented using a\n`region-`\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e syntax.\nAny [dataset location name](/bigquery/docs/locations) can be used for\n\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e. For example, the following region qualifiers\nare valid:\n\n- `region-us`\n- `region-asia-east2`\n- `region-europe-north1`\n\nWhen present, a region qualifier restricts results to the specified\nlocation. For example, the following query returns metadata for all datasets in a\nproject in the `US` multi-region: \n\n```googlesql\n-- Returns metadata for all datasets in a region.\nSELECT * FROM region-us.INFORMATION_SCHEMA.SCHEMATA;\n```\n\nThe following `INFORMATION_SCHEMA` views don't support region qualifiers:\n\n- [`INFORMATION_SCHEMA.PARTITIONS`](/bigquery/docs/information-schema-partitions#scope_and_syntax)\n- [`INFORMATION_SCHEMA.SEARCH_INDEXES`](/bigquery/docs/information-schema-indexes#scope_and_syntax)\n- [`INFORMATION_SCHEMA.SEARCH_INDEX_COLUMNS`](/bigquery/docs/information-schema-index-columns)\n- [`INFORMATION_SCHEMA.SEARCH_INDEX_OPTIONS`](/bigquery/docs/information-schema-index-options)\n\nIf neither a region qualifier nor a dataset qualifier is specified, you will\nreceive an error.\n\nQueries against a region-qualified `INFORMATION_SCHEMA` view run in the region that you specify, which means that you can't write a single query to join data from views in different regions. To combine `INFORMATION_SCHEMA` views from multiple regions, read and combine the query results locally, or [copy](/bigquery/docs/managing-tables#copy_tables_across_regions) the resulting tables to a common region.\n\n### Project qualifier\n\nWhen present, a project qualifier restricts results to the specified project.\nFor example: \n\n -- Returns metadata for the specified project and region.\n SELECT * FROM myProject.`region-us`.INFORMATION_SCHEMA.TABLES;\n\n -- Returns metadata for the specified project and dataset.\n SELECT * FROM myProject.myDataset.INFORMATION_SCHEMA.TABLES;\n\nAll `INFORMATION_SCHEMA` views support project qualifiers. If a project\nqualifier is not specified, the view will default to the\nproject in which the query is executing.\n\nSpecifying a project qualifier for organization-level views\n(e.g. `STREAMING_TIMELINE_BY_ORGANIZATION`)\nhas no impact on the results.\n\nLimitations\n-----------\n\n- BigQuery `INFORMATION_SCHEMA` queries must be in GoogleSQL syntax. `INFORMATION_SCHEMA` does not support legacy SQL.\n- `INFORMATION_SCHEMA` query results are not cached.\n- `INFORMATION_SCHEMA` views cannot be used in DDL statements.\n- `INFORMATION_SCHEMA` views don't contain information about [hidden datasets](/bigquery/docs/datasets#hidden_datasets).\n- `INFORMATION_SCHEMA` queries with region qualifiers might include metadata from resources in that region from [deleted datasets that are within your time travel window](/bigquery/docs/restore-deleted-datasets).\n- When you list resources from an `INFORMATION_SCHEMA` view, the permissions are checked only at the parent level, not at an individual row level. Therefore, any [deny policy](/bigquery/docs/control-access-to-resources-iam#deny_access_to_a_resource) ([preview](/products#product-launch-stages)) that conditionally targets an individual row using tags is ignored."]]
