DB2 V9 SQL跨平台开发参考手册

需积分: 10 97 浏览量更新于2024-07-29 收藏 9.1MB PDF 举报

DB2_V9_SQL 是一本专为多平台开发设计的DB2关系数据库产品的参考手册，适用于多个版本：DB2 for z/OS的Version 9、DB2 for i的Version 6.1以及DB2在Linux、UNIX和Windows平台上的Version 9.5。该文档是IBM的专有信息，受版权保护，并在许可协议下提供。用户在使用前应阅读第941页的“注意事项”部分，了解通用信息。本手册涵盖了以下关键知识点： 1. **DB2 Version 9**：针对大型机环境（如z/OS）的DB2版本，它提供了高性能、高可用性和安全性，支持企业级数据管理，可能包括SQL语言的深入细节、存储过程、事务处理和联接操作等。 2. **DB2 for i Version 6.1**：面向IBM i系统的DB2版本，适应了中型企业环境，可能包含特定于iSeries的特性，如集成操作系统功能和定制化的应用程序接口。 3. **DB2 for Linux, UNIX, and Windows Platforms Version 9.5**：这是跨平台版本，强调兼容性和灵活性，适合运行在多种操作系统环境下的应用，可能涉及SQL在不同环境中的优化、性能调优和平台特性的整合。 4. **通用信息与限制**：手册包含了产品使用的基本指南，同时也指出任何产品声明不应视为保修，且受限于GSA Schedule Contract与IBM Corp.的协议，美国政府用户受到特定使用、复制和披露权限的约束。 5. **目标读者**：这本书适合数据库管理员、开发人员、系统架构师和技术支持人员，特别是那些需要理解和使用DB2 SQL语句、查询优化以及进行跨平台开发的人员。 6. **目录结构**：手册可能按章节组织，涵盖SQL语法、查询操作、数据定义、数据操纵、安全性、备份恢复、性能管理和故障排查等内容，以便读者系统学习和查阅。通过阅读DB2_V9_SQL，用户可以获得深入理解DB2在不同平台上的核心功能，以及如何有效地利用这些功能进行高效的数据管理和应用程序开发。同时，它也提醒用户在实际操作中注意法律和合同条款，确保合规使用。

DB2 for IBM i

v DB2 for i SQL Reference

v DB2 for i SQL Programming

v DB2 for i Embedded SQL Programming

v IBM Developer Kit for Java topic in the System i Information Center

v System i Information Center, at http://publib.boulder.ibm.com/iseries/

DB2 for the Linux, UNIX and Windows Platforms

v IBM DB2 Version 9.5 for Linux, UNIX

, and Windows SQL Reference, Volumes 1

and 2

v IBM DB2 Version 9.5 for Linux, UNIX, and Windows Getting Started with Database

Application Development

v IBM DB2 Version 9.5 for Linux, UNIX, and Windows Developing Embedded SQL

Applications

v IBM DB2 Version 9.5 for Linux, UNIX, and Windows Developing SQL and External

Routines

v DB2 Information Center, at http://publib.boulder.ibm.com/infocenter/db2luw/

v9r5/

Distributed relational database architecture

v Application Programming Guide, SC26-4773

v Connectivity Guide, SC26-4783

v Open Group Publications: DRDA Vol. 1: Distributed Relational Database Architecture

(DRDA), at http://www.opengroup.org/publications/catalog/c066.htm.

v Open Group Publications: DRDA Vol. 2: Formatted Data Object Content Architecture

(FD:OCA), at http://www.opengroup.org/publications/catalog/c067.htm.

v Open Group Publications: DRDA Vol. 3: Distributed Data Management (DDM)

Architecture, at http://www.opengroup.org/publications/catalog/c068.htm.

Character data representation architecture

v Character Data Representation Architecture Reference and Registry, SC09-2190

Unicode standard

v The Unicode Standard, at http://www.unicode.org.

Industry standards

v ISO/IEC FCD 9075-1:2003, Information technology - Database languages - SQL - Part

1: Framework (SQL/Framework)

v ISO/IEC FCD 9075-2:2003, Information technology - Database languages - SQL - Part

2: Foundation (SQL/Foundation)

v ISO/IEC FCD 9075-3:2003, Information technology - Database languages - SQL - Part

3: Call-Level Interface (SQL/CLI)

v ISO/IEC FCD 9075-4:2003, Information technology - Database languages - SQL - Part

4: Persistent Stored Modules (SQL/PSM)

v ISO/IEC FCD 9075-9:2003, Information technology - Database languages - SQL - Part

9: Management of External Data (SQL/MED)

v ISO/IEC FCD 9075-10:2003, Information technology - Database languages - SQL - Part

10: Object Language Bindings (SQL/OLB)

v ISO/IEC FCD 9075-11:2003, Information technology - Database languages - SQL - Part

11: Information and Definition Schemas (SQL/Schemata)

Highlighting conventions

xiv DB2 SQL Reference for Cross-Platform Development Version 3.1

Chapter 1. Concepts

This chapter provides a high-level view of concepts that are important to

understand when using Structured Query Language (SQL). The reference material

contained in the rest of this manual provides a more detailed view.

Relational database

A relational database is a database that can be perceived as a set of tables and can be

manipulated in accordance with the relational model of data. The relational

database contains a set of objects used to store, access, and manage data. The set of

objects includes tables, views, indexes, aliases, distinct types, functions, procedures,

sequences, and packages. Any number of relational databases can be created on a

given physical machine.

Structured query language

Structured Query Language (SQL) is a standardized language for defining and

manipulating data in a relational database. In accordance with the relational model

of data, the database is perceived as a set of tables, relationships are represented by

values in tables, and data is retrieved by specifying a result table that can be

derived from one or more base tables.

SQL statements are executed by a database manager. One of the functions of the

database manager is to transform the specification of a result table into a sequence

of internal operations that optimize data retrieval. This transformation occurs when

the SQL statement is prepared. This transformation is also known as binding.

All executable SQL statements must be prepared before they can be executed. The

result of preparation is the executable or operational form of the statement. The

method of preparing an SQL statement and the persistence of its operational form

distinguish static SQL from dynamic SQL.

Static SQL

The source form of a static SQL statement is embedded within an application

program written in one of the supported host languages; COBOL, C (C also covers

C++ in this documentation, unless otherwise mentioned explicitly) or Java

™

. The

statement is prepared before the program is executed and the operational form of

the statement persists beyond the execution of the program.

A source program containing static SQL statements must be processed by an SQL

precompiler before it is compiled. The precompiler checks the syntax of the SQL

statements, turns them into host language comments, and generates host language

statements to invoke the database manager.

The preparation of an SQL application program includes precompilation, the

preparation of its static SQL statements, and compilation of the modified source

program. The exact steps required are product-specific.

Dynamic SQL

Programs containing embedded dynamic SQL statements must be precompiled like

those containing static SQL, but unlike static SQL, the dynamic SQL statements are

constructed and prepared at run time. The source form of a dynamic statement is a

character string that is passed to the database manager by the program using the

static SQL PREPARE or EXECUTE IMMEDIATE statement. A statement prepared

using the PREPARE statement can be referenced in a DECLARE CURSOR,

DESCRIBE, or EXECUTE statement. The operational form of the statement persists

for the duration of the connection. For DB2 for z/OS it only persists for the

duration of the transaction.

SQL statements embedded in a REXX application are dynamic SQL statements.

SQL statements submitted to an interactive SQL facility and to the Call Level

Interface (CLI) are also dynamic SQL statements.

Interactive SQL

An interactive SQL facility is associated with every database manager. Essentially,

every interactive SQL facility is an SQL application program that reads statements

from a workstation, prepares and executes them dynamically, and displays the

results to the user. Such SQL statements are said to be issued interactively.

For example, the following facilities provide interactive capabilities:

v SPUFI for DB2 for z/OS

v System i

™

Navigator, Interactive SQL, or Query Manager for DB2 for i.

v Command Line Processor or Command Center for DB2 for LUW.

SQL call level interface and open database connectivity

The DB2 Call Level Interface (CLI) is an application programming interface in

which functions are provided to application programs to process dynamic SQL

statements. DB2 CLI allows users to access SQL functions directly through a call

interface. CLI programs can also be compiled using an Open Database

Connectivity (ODBC) Software Developer’s Kit, available from Microsoft

or other

vendors, enabling access to ODBC data sources. Unlike using embedded SQL, no

precompilation is required. Applications developed using this interface may be

executed on a variety of databases without being compiled against each of the

databases. Through the interface, applications use procedure calls at execution time

to connect to databases, to issue SQL statements, and to get returned data and

status information.

For a complete description of all the available functions, see the product books.

Java database connectivity and embedded SQL for Java

programs

DB2 provides two standards-based Java programming APIs: Java Database

Connectivity (JDBC) and embedded SQL for Java (SQLJ). Both can be used to

create Java applications and applets that access DB2.

Static SQL cannot be used by JDBC. SQLJ applications use JDBC as a foundation

for such tasks as connecting to databases and handling SQL errors, but can also

contain embedded static SQL statements in the SQLJ source files. An SQLJ source

file has to be translated with the SQLJ translator before the resulting Java source

code can be compiled.

For more information about JDBC and SQLJ applications, see the product books.

Concepts

2 DB2 SQL Reference for Cross-Platform Development Version 3.1

剩余979页未读，继续阅读

五柳-先生

粉丝: 251
资源: 168

DB2 V9 SQL跨平台开发参考手册

DB2_V9维护手册

DB2 V9 课程.rar

db2_v101_winx64_expc

DB2_COMPATIBILITY_VECTOR

db2_svr_10.5.0.3_linux_x86-64pvu.tar.gz

DB2数据库使用shell脚本如何判断指定表数据是否存在

致命错误: Call to undefined function app\admin\controller\db2_connect()

配置文件写两个oracle

postgresql dblink跨库联表分页查询

最新资源