ISO/IEC 9075-11:2023/Cor 1:2026

• Status: Published
• Publication Date: 02-Aug-2026
• ICS: 35.060 - Languages used in information technology
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 3 - Database language
• Current Stage: 6060 - International Standard published
• Start Date: 03-Aug-2026
• Completion Date: 03-Aug-2026

• Corrects: ISO/IEC 9075-11:2023 - Information technology — Database languages SQL — Part 11: Information and definition schemas (SQL/Schemata)
• Effective Date: 07-Jan-2026

ISO/IEC 9075-11:2023/Cor 1:2026 is an ISO technical corrigendum to Part 11 of the SQL standard, Information and definition schemas (SQL/Schemata). It corrects the published rules for the DefinitionSchema clause, especially the INFORMATION_SCHEMA base tables used by SQL implementations to describe routines and implementation limits.

What does ISO/IEC 9075-11:2023/Cor 1:2026 specify?

ISO/IEC 9075-11:2023/Cor 1:2026 specifies corrections to ISO/IEC 9075-11:2023, with all changes concentrated in Clause 7, DefinitionSchema. The corrigendum updates three base tables used by SQL metadata: ROUTINES, SQL_IMPLEMENTATION_INFO, and SQL_SIZING.

Clause/item	What it covers
7.46 ROUTINES base table	Corrects the definition of NEW_SAVEPOINT_LEVEL and its value meanings
7.50 SQL_IMPLEMENTATION_INFO base table	Corrects description text and initial table population, including a SEARCH PATTERN ESCAPE row
7.51 SQL_SIZING base table	Corrects description text and clarifies initial table population for supported sizes

In practice, this document matters to anyone implementing or validating SQL schema metadata. It tells them how the standard’s INFORMATION_SCHEMA tables are to be populated and how specific metadata values are to be interpreted.

What are the key requirements of ISO/IEC 9075-11:2023/Cor 1:2026?

ISO/IEC 9075-11:2023/Cor 1:2026 makes targeted corrections rather than introducing new features. The most important changes affect how implementations declare routine savepoint behavior and how they report implementation and sizing information.

ROUTINES base table

Clause 7.46 changes the NEW_SAVEPOINT_LEVEL column definition so that it is NOT NULL and uses the INFORMATION_SCHEMA.YES_OR_NO type. For implementers, this means the column must always be populated in the base table.

The corrigendum also replaces the value description for NEW_SAVEPOINT_LEVEL. YES means the SQL-invoked routine is an SQL-invoked function or an SQL-invoked procedure that specifies NEWSAVEPOINTLEVEL. NO means the SQL-invoked routine is an SQL-invoked procedure that does not specify NEWSAVEPOINTLEVEL or specifies OLDSAVEPOINTLEVEL. This matters when building INFORMATION_SCHEMA views and when testing routine metadata.

SQL_IMPLEMENTATION_INFO base table

Clause 7.50 revises the description text for IMPLEMENTATION_INFO_ID values so that the wording about backwards compatibility aligns with the ISO/IEC 9075 series. It also corrects the initial table population text so that implementations populate the base table with an equivalent INSERT statement.

The corrigendum adds an initial-population item defining ESC as the escape character and inserts a row for SEARCH PATTERN ESCAPE. In practice, this gives implementers a concrete metadata entry to include when they report support for escape characters in search patterns.

SQL_SIZING base table

Clause 7.51 corrects the description text for SIZING_ID values and clarifies how the SQL_SIZING base table is populated. For supported facilities, the SUPPORTED_VALUE column holds the maximum size or limit supported by the SQL implementation; for unsupported information items, it is null. The COMMENTS column may contain an implementation-chosen note or null.

The corrected initial population covers a set of sizing items such as maximum catalog name length, column name length, columns in GROUP BY, ORDER BY and SELECT, concurrent activities, cursor name length, driver connections, identifier length, schema name length, statement octets, table name length, tables in SELECT, user name length, and several current length limits. For users, this is the part that tells them what size and capacity metadata the implementation is expected to expose.

What terms does ISO/IEC 9075-11:2023/Cor 1:2026 define?

• SQL-invoked routine - A routine whose savepoint-level behavior is reported in the ROUTINES base table.
• SQL-invoked function - An SQL-invoked routine that specifies NEWSAVEPOINTLEVEL.
• SQL-invoked procedure - An SQL-invoked routine that may specify NEWSAVEPOINTLEVEL or OLDSAVEPOINTLEVEL.
• NEWSAVEPOINTLEVEL - The newer savepoint-level setting whose presence is reported as YES in the corrected ROUTINES definition.
• OLDSAVEPOINTLEVEL - The older savepoint-level setting that leads to NO in the corrected ROUTINES definition.
• IMPLEMENTATION_INFO_ID - The identifier used in SQL_IMPLEMENTATION_INFO to name implementation capability items.
• SIZING_ID - The identifier used in SQL_SIZING to name capacity and limit items.
• SUPPORTED_VALUE - The value in SQL_SIZING that records the maximum supported size or limit for a sizing item.

Who uses ISO/IEC 9075-11:2023/Cor 1:2026?

ISO/IEC 9075-11:2023/Cor 1:2026 is used by SQL database engine vendors, standards implementers, and conformance test teams. It is also relevant to quality managers and system integrators who check whether a DBMS reports INFORMATION_SCHEMA metadata consistently.

Typical tasks include:

• populating ROUTINES, SQL_IMPLEMENTATION_INFO, and SQL_SIZING correctly
• verifying metadata queries against the SQL standard
• checking routine behavior reporting, including savepoint-level flags
• documenting supported limits such as identifier length or statement length
• aligning implementation notes with the ISO/IEC 9075 series

What changed in ISO/IEC 9075-11:2023/Cor 1:2026 from the previous edition?

ISO/IEC 9075-11:2023/Cor 1:2026 is a Technical Corrigendum to ISO/IEC 9075-11:2023. It changes the ROUTINES, SQL_IMPLEMENTATION_INFO, and SQL_SIZING clauses by correcting column definitions, description text, and initial table population details.

Which standards are used with ISO/IEC 9075-11:2023/Cor 1:2026?

The corrigendum refers to the ISO/IEC 9075 series, and it specifically mentions backwards compatibility with ISO/IEC 9075-3:1995 in the corrected description text. That reference matters for understanding why some IMPLEMENTATION_INFO_ID and SIZING_ID values are retained.

What does the ISO/IEC 9075-11:2023/Cor 1:2026 document contain?

The document contains replacement wording for a column definition, revised value descriptions, and corrected table-population text for SQL metadata tables. It includes an updated NOT NULL constraint for NEW_SAVEPOINT_LEVEL, corrected explanatory text for IMPLEMENTATION_INFO_ID and SIZING_ID values, and an added insert-row example for SEARCH PATTERN ESCAPE.

It also gives the population logic for SQL_SIZING, including how supported and unsupported items are represented. For implementers, this is the part to use when updating schema metadata generation or conformance checks.

International
Standard
ISO/IEC 9075-11
Fifth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 11:
CORRIGENDUM 1
Information and definition schemas
2026-08
(SQL/Schemata)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données
SQL —
Partie 11: Schémas des informations et des définitions (SQL/
Schemata)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-11:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-11:2023/Cor. 1:2026(en)
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC 9075-11:2023/Cor.1:2026(en)
Technical Corrigendum 1 to ISO/IEC 9075-11:2023 was prepared by Joint Technical Committee ISO/IEC JTC
1, Information technology, Subcommittee SC 32, Data management and interchange.
© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC 9075-11:2023/Cor. 1:2026(en)
7 DefinitionSchema
7.46 ROUTINESbasetable
1. Rationale: AddmissingNOTNULLconstraint.
IntheDefinition,replacethecolumndefinitionofNEW_SAVEPOINT_LEVELwith:
NEW_SAVEPOINT_LEVEL INFORMATION_SCHEMA.YES_OR_NO
CONSTRAINT NEW_SAVEPOINT_LEVEL_NOT_NULL
NOT NULL,
2. Rationale: AdjustforNOTNULLconstraint.
ReplaceDescription21)with:
21) ThevaluesofNEW_SAVEPOINT_LEVELhavethefollowingmeanings:
YES TheSQL-invokedroutineisanSQL-invokedfunctionorisanSQL-invoked
procedurethatspecifiesNEWSAVEPOINTLEVEL.
NO TheSQL-invokedroutineisanSQL-invokedprocedurethatdoesnotspecify
NEWSAVEPOINTLEVELorspecifiesOLDSAVEPOINTLEVEL.
7.50 SQL_IMPLEMENTATION_INFObasetable
1. Rationale: RemoveincorrectsentenceinDescription.
ReplaceDescription3)with:
3) SomeIMPLEMENTATION_INFO_IDvaluesassignedbytheISO/IEC9075serieshavebeen
assignedforbackwardscompatibilitywithISO/IEC9075-3:1995.
2. Rationale: RemoveincorrectsentenceinInitialTablePopulation.
ReplaceInitialTablePopulation2)with:
2) TheSQL-implementationshalleffectivelypopulatetheSQL_IMPLEMENTATION_INFObase
tablewithanthatisequivalenttotheshownbelow.
3. Rationale: AddmissingInitialTablePopulationitem.
AddthefollowingInitialTablePopulation.
3) .
m) LetESCbeacharacterthatrepresentstheescapecharacter.
4. Rationale: AddmissingInitialTablePopulationitem.
Insertthefollowingrowin“VALUES”inInitialTablePopulation4):
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-11:2023/Cor. 1:2026(en)
( 14, 'SEARCH PATTERN ESCAPE', NULL, ESC, 'The escape character' ),
7.51 SQL_SIZINGbasetable
1. Rationale: Removeincor
...