ISO/IEC 9075-9: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-9:2023 - Information technology — Database languages SQL — Part 9: Management of External Data (SQL/MED)
• Effective Date: 07-Jan-2026

ISO/IEC 9075-9:2023/Cor 1:2026 is an ISO/IEC technical corrigendum to the SQL/MED part of the SQL database-language series. It corrects selected points in the management of external data provisions, especially the SQL_SIZING basetable and the conformance rules for SQL/MED. It is aimed at implementers, database vendors, and conformance testers who need the corrected text for compliant behavior and claims.

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

ISO/IEC 9075-9:2023/Cor 1:2026 specifies corrections to ISO/IEC 9075-9:2023, not a new feature set. The corrigendum updates Clause 25 on the SQL_SIZING basetable, Clause 27 on conformance, and Table 38 on implied feature relationships.

In practice, the document tells readers exactly what to insert, delete, or replace in the base edition. That matters because SQL/MED implementations, conformance statements, and feature dependency checks should follow the corrected text rather than the uncorrected edition.

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

• Clause 25.12, SQL_SIZING basetable adds a new initial table population entry for MAXIMUM DATALINK LENGTH. In practice, implementations need to carry that sizing item in the SQL_SIZING basetable so that the database reports the supported datalink length in the expected way.

• The same Clause 25.12 correction ties that sizing item to a value expressed in octets. For implementers, this means the sizing information is about byte-length reporting, which is relevant when external data links are created, checked, or documented.

• Clause 27.1, Claims of conformance to SQL/MED deletes one bullet item from the list of conformance claims. In practice, this narrows the set of statements an implementation can use when asserting SQL/MED conformance.

• Clause 27.2, Additional conformance requirements for SQL/MED removes an incorrect implied feature relationship for feature M002 Datalinks via SQL/CLI. This matters because conformance logic should no longer treat the old one-to-one dependency as the rule.

• The same Table 38 correction replaces that relationship with a broader one: feature M002 Datalinks via SQL/CLI implies at least one CLI routine invocation environment from the listed host languages. In practice, an implementation claiming M002 needs to support SQL/CLI routine invocation in one of the named languages, not only one fixed language path.

• The listed host languages for that implied relationship are Ada, C, COBOL, Fortran, MUMPS, Pascal, and PL/I. For engineering and procurement teams, this is the detail that shows which integration environments can satisfy the SQL/CLI datalink feature.

• The corrigendum keeps the focus on correcting dependencies and catalog initialization, not on changing the underlying SQL/MED model. That means test plans and compliance checklists should be updated to match the corrected conformance text.

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

• SQL/MED - SQL/MED means SQL management of external data, the subject area covered by Part 9 of ISO/IEC 9075.

• SQL_SIZING basetable - The SQL_SIZING basetable is the sizing table that records implementation limits and support values used by SQL/MED.

• InitialTablePopulation - InitialTablePopulation is the catalog population step referenced in Clause 25.12, where the corrigendum adds a new sizing entry.

• Claims of conformance to SQL/MED - These are the formal statements an implementation can make about complying with SQL/MED, and the corrigendum adjusts the allowed wording by removing one option.

• Datalinks via SQL/CLI - This is feature M002, the SQL/MED feature that relates datalinks to the SQL Call-Level Interface.

• SQL/CLI - SQL/CLI is the SQL Call-Level Interface, the API-style interface used by host languages to invoke SQL routines.

• Implied feature relationship - An implied feature relationship is a dependency rule showing what other features must be available when a feature is supported.

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

ISO/IEC 9075-9:2023/Cor 1:2026 is used by database software vendors, SQL engine implementers, and teams that maintain SQL/MED support. It is also relevant to quality managers and conformance testers who verify feature claims, especially for SQL/CLI-based datalinks and catalog population behavior.

Organizations that update certification test plans, product documentation, or interoperability claims use this corrigendum to keep those materials aligned with the corrected standard text. That matters when a product must state what it supports and how that support is implemented.

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

ISO/IEC 9075-9:2023/Cor 1:2026 is a technical corrigendum to ISO/IEC 9075-9:2023. It states three corrections: a new SQL_SIZING basetable entry for MAXIMUM DATALINK LENGTH, a deletion from the conformance claims list in Clause 27.1, and a revised implied feature relationship for M002 in Table 38.

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

• ISO/IEC 9075-9:2023 - the base edition being corrected by this technical corrigendum; it provides the underlying SQL/MED requirements that the corrigendum amends.

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

The document contains front matter and a set of correction instructions prepared for ISO/IEC JTC 1/SC 32. Its technical content is organized as clause-level changes with a short rationale before each correction, showing what to replace, delete, or insert.

It includes one insertion in Clause 25.12, one deletion in Clause 27.1, and a revised row in Table 38 for feature M002. For readers who test or audit implementations, these are the places to check against the base edition when updating SQL/MED behavior, conformance statements, and dependency rules.

International
Standard
ISO/IEC 9075-9
Fifth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 9:
CORRIGENDUM 1
Management of External Data (SQL/
2026-08
MED)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données
SQL —
Partie 9: Gestion des données externes (SQL/MED)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-9:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-9: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-9:2023/Cor.1:2026(en)
Technical Corrigendum 1 to ISO/IEC 9075-9: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-9:2023/Cor. 1:2026(en)
25 DefinitionSchema
25.12SQL_SIZINGba
...