> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/query-metadata-from-a-database-article/options-query-from-database/input-tab.md). # Input tab ![Query metadata from Database step Input tab](/files/fZ1o4tu3C7bl9DWwNGiX) You use the **Input** tab to filter the results using specific values for each argument presented in the tab. There are two options. | Option | Description | | ------------------- | ---------------------------------------------------------------------------- | | **Enter Arguments** | Enter a value for a specific argument. | | **From Fields** | Select any fields that are currently available in the transformation stream. | ## Enter Arguments You use this option to add values to an argument to use to filter the results. See the following table for the argument options for each **JDBC Metadata Discovery Type**. | Discovery type | Argument options | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Catalog** | No options | N/A | | **Schemas** | **Catalog** | Specify the name of the catalog to limit the results. If left empty, all schemas from all catalogs are returned. | | **Schema Pattern** | Specify a pattern to limit the schemas to return. If empty, the tables from all schemas are returned. % matches 0 or more characters and \_ matches exactly 1 character. | | | **Tables** | **Catalog** | Specify the name of the catalog to limit the results. If left empty, all schemas from all catalogs are returned. | | **Schema Pattern** | Specify a pattern to limit the schemas to return. If empty, the tables from all schemas are returned. % matches 0 or more characters and \_ matches exactly 1 character. | | | **Table Pattern** | A pattern limiting the tables to return. If empty, all tables are returned. % matches 0 or more characters and \_ matches exactly 1 character. | | | **Table Types** | Specify a comma delimited list of table types to limit the results. | | | **Columns** | **Catalog** | Specify the name of the catalog to limit the results. If left empty, all columns from all catalogs are returned. | | **Schema Pattern** | Specify a pattern to limit the schemas to return. If empty, the columns from all schemas are returned. % matches 0 or more characters and \_ matches exactly 1 character. | | | **Table Pattern** | Specify a pattern to limit the columns returned. This usually follows the database's LIKE syntax, but may vary depending on the JDBC driver used. | | | **Column Pattern** | Specify a pattern to limit the columns to return. If empty, all tables are returned. % matches 0 or more characters and \_ matches exactly 1 character. | | | **Primary Keys** | **Catalog** | Specify the name of the catalog to limit the results. If left empty, all schemas from all catalogs are returned. | | **Schema** | Specify the name of the schema to limit the results. | | | **Table** | Specify the name of the table to limit the results. | | | **Foreign Keys** | **Catalog** | Specify the name of the catalog to limit the results. If left empty, all schemas from all catalogs are returned. | | **Schema** | Specify the name of the schema to limit the results | | | **Table** | Specify the name of the table to limit the results. | | ## From Fields You use this option to specify fields within the transformation stream to filter the results. Select a value in one or more of the dropdown menus. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/query-metadata-from-a-database-article/options-query-from-database/input-tab.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.