DATASET_ID: 데이터 세트의 ID입니다. 자세한 내용은 데이터 세트 한정자를 참조하세요.
예시
-- Returns metadata for parameters of a routine in a single dataset.SELECT*FROMmyDataset.INFORMATION_SCHEMA.PARAMETERS;-- Returns metadata for parameters of a routine in a region.SELECT*FROMregion-us.INFORMATION_SCHEMA.PARAMETERS;
예
예
기본 프로젝트가 아닌 다른 프로젝트의 데이터 세트에 대해 쿼리를 실행하려면 다음 형식으로 프로젝트 ID를 추가하세요.
[[["이해하기 쉬움","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-08-26(UTC)"],[[["\u003cp\u003eThe \u003ccode\u003eINFORMATION_SCHEMA.PARAMETERS\u003c/code\u003e view provides details about each parameter of every routine within a dataset.\u003c/p\u003e\n"],["\u003cp\u003eQuerying this view requires specific IAM permissions, including \u003ccode\u003ebigquery.routines.get\u003c/code\u003e and \u003ccode\u003ebigquery.routines.list\u003c/code\u003e, which are included in predefined roles like \u003ccode\u003eroles/bigquery.admin\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eEach row in the view corresponds to a single parameter, offering information such as the parameter's name, data type, position, mode, and whether it's a result or not.\u003c/p\u003e\n"],["\u003cp\u003eQueries against \u003ccode\u003eINFORMATION_SCHEMA.PARAMETERS\u003c/code\u003e must include either a dataset or a region qualifier to specify the scope of the data.\u003c/p\u003e\n"],["\u003cp\u003eThe view can be queried at both the project and dataset level, with region qualifiers needed for project-level queries, and the query execution location must match the region of the \u003ccode\u003eINFORMATION_SCHEMA\u003c/code\u003e view.\u003c/p\u003e\n"]]],[],null,["# PARAMETERS view\n===============\n\nThe `INFORMATION_SCHEMA.PARAMETERS` view contains one row for each parameter of\neach routine in a dataset.\n\nRequired permissions\n--------------------\n\nTo query the `INFORMATION_SCHEMA.PARAMETERS` view, you need the following\nIdentity and Access Management (IAM) permissions:\n\n- `bigquery.routines.get`\n- `bigquery.routines.list`\n\nEach of the following predefined IAM roles includes the\npermissions that you need to get routine metadata:\n\n- `roles/bigquery.admin`\n- `roles/bigquery.metadataViewer`\n- `roles/bigquery.dataViewer`\n\nFor more information about BigQuery permissions, see\n[Access control with IAM](/bigquery/docs/access-control).\n\nSchema\n------\n\nWhen you query the `INFORMATION_SCHEMA.PARAMETERS` view, the query results\ncontain one row for each parameter of each routine in a dataset.\n\nThe `INFORMATION_SCHEMA.PARAMETERS` view has the following schema:\n\nScope and syntax\n----------------\n\nQueries against this view must include a dataset or a region qualifier. For more\ninformation see [Syntax](/bigquery/docs/information-schema-intro#syntax).\nThe following table explains the region and resource scopes for this view:\n\nReplace the following:\n\n- Optional: \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of your Google Cloud project. If not specified, the default project is used.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: any [dataset region name](/bigquery/docs/locations). For example, ```region-us```.\n- \u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e: the ID of your dataset. For more information, see [Dataset qualifier](/bigquery/docs/information-schema-intro#dataset_qualifier).\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n | **Note:** You must use [a region qualifier](/bigquery/docs/information-schema-intro#region_qualifier) to query `INFORMATION_SCHEMA` views. The location of the query execution must match the region of the `INFORMATION_SCHEMA` view.\n\n\u003cbr /\u003e\n\n**Example** \n\n -- Returns metadata for parameters of a routine in a single dataset.\n SELECT * FROM myDataset.INFORMATION_SCHEMA.PARAMETERS;\n\n -- Returns metadata for parameters of a routine in a region.\n SELECT * FROM region-us.INFORMATION_SCHEMA.PARAMETERS;\n\nExample\n-------\n\n#### Example\n\nTo run the query against a dataset in a project other than your default project,\nadd the project ID in the following format: \n\n```bash\n`PROJECT_ID`.`DATASET_ID`.INFORMATION_SCHEMA.PARAMETERS\n```\nReplace the following:\n\n\u003cbr /\u003e\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project.\n- \u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e: the ID of the dataset.\n\nFor example, `example-project.mydataset.INFORMATION_SCHEMA.JOBS_BY_PROJECT`.\n\nThe following example retrieves all parameters from the\n`INFORMATION_SCHEMA.PARAMETERS` view. The metadata returned is for routines in\n`mydataset` in your default project --- `myproject`. \n\n```googlesql\nSELECT\n * EXCEPT(is_typed)\nFROM\n mydataset.INFORMATION_SCHEMA.PARAMETERS\nWHERE\n table_type = 'BASE TABLE';\n```\n| **Note:** `INFORMATION_SCHEMA` view names are case-sensitive.\n\nThe result is similar to the following: \n\n```\n+-------------------+------------------+---------------+------------------+----------------+-----------+----------------+-----------+-------------------+--------------+\n| specific_catalog | specific_schema | specific_name | ordinal_position | parameter_mode | is_result | parameter_name | data_type | parameter_default | is_aggregate |\n+-------------------+------------------+---------------+------------------+----------------+-----------+----------------+-----------+-------------------+--------------+\n| myproject | mydataset | myroutine1 | 0 | NULL | YES | NULL | INT64 | NULL | NULL |\n| myproject | mydataset | myroutine1 | 1 | NULL | NO | x | INT64 | NULL | NULL |\n+-------------------+------------------+---------------+------------------+----------------+-----------+----------------+-----------+-------------------+--------------+\n```"]]
