Free Design Tool
Get help with your business process or SOA design. Use this free online tool to get new design ideas or to verify your design decomposition. More...
Posts on the
Design Decomposition Blog
Changes for IT and Regulatory Requirements
This post picks up on two ideas in my last post. The first  idea is that IT will have significant change, in part, from the adoption of Cloud Computing. Take a look at IT Departments Won’t Exist in Five Years at Computerworld.com. It states that: Consumerization of IT and self-service trends will lead to a [...]
June 12, 2013
Cloud Users View of Security
Two recent surveys (details below) support the driving and restraining forces related to security shown in the Force Field Analysis for Using a Public Cloud instead of an In-House Private Cloud posted a couple weeks ago. Participants in both surveys were Cloud users. Data supporting the driving forces: The TechInsights Report 2013: Cloud Succeeds stated [...]
June 9, 2013
Using a Public Cloud instead of an In-House Private Cloud
Last April, Jason Bloomberg of ZapThink issued a ZapFlash titled Cloud Computing: Rethinking Control of IT. I thought it would be useful to organize his arguments into a Force Field Analysis as described in Web Services, Service-Oriented Architectures, and Cloud Computing. The following analysis also includes information from two other ZapFlash entries that Jason referenced [...]
June 5, 2013
Five Principles for the Incremental SOA Analysis
After last week’s posting, I thought I should say more about incremental SOA analysis. The following is from Chapter 10 in Web Services, Service-Oriented Architectures, and Cloud Computing. Service-oriented architecture (SOA) projects are no different from other IT projects in that larger projects tend to fail and issues regarding change can scuttle projects. This chapter [...]
May 29, 2013
Incremental SOA and Change
Computerworld had an article last January that discussed American Airlines’ approach to using Web Services and multiple enterprise service buses (ESBs) as part of their service-oriented architecture (SOA). The authors emphasized a change from build vs. buy and from using mainframes. That, however, is not the part I found interesting. (Also, several comments to the [...]
May 22, 2013
INCITS

SQL-92 was developed by the INCITS Technical Committee H2 on Database. This committee develops standards for the syntax and semantics of database languages.

SQL-92 was designed to be a standard for relational database management systems (RDBMSs). It is based SQL-89, which in turn was based on SQL-86. SQL-92 was developed by the ANSI (then NCITS, and now INCITS) X3H2 committee, which originally began work on a SQL standard in 1982.

SQL-92 does not address objects in any way. Nevertheless, SQL-92 forms the basis for JDBC, SQLJ, SQL:1999, and ODMG OQL. Each of these specifications are covered in other parts of this section. See the related content below.

SQL is a database sublanguage that is used for accessing relational databases. The letters don't stand for anything.1 A database sublanguage is one that is used in association with some other language for the purpose of accessing a database. This results in a programming style illustrated by the embedded SQL statements in the following diagram.

Embedded database sublanguage

An example of an embedded SQL statement that creates a new Person instance would be:

EXEC SQL BEGIN DECLARE SECTION;
    char SQLSTATE[6];
    char ssan[9];
    char name[30];
EXEC SQL END DECLARE SECTION

EXEC SQL
INSERT INTO person VALUES (:ssan, :name);

This code would be in addition to any host programming code. The variables :ssan and :name would need to be set by the host program using the host programming language before execution. If you also wanted to manipulate this new Person instance in the host program, you would need programming code in addition to this code fragment that populates the instance in the programming language along with the instance in the database.

>>
Also see the INCITS DM32.2 Task Group on Database website.

1. According to Jim Melton, the editor of the SQL standard, the proper pronunciation is "ess cue ell," and not "sequel" as is commonly heard. Jim also says that SQL stands for "SQL Query Language" and notes that this is a recursive acronym. In some early prototypes, SQL stood for "Structured Query Language." That is not true for the standard.

Related Articles

More on the general topic: DBMS Standards

Douglas K Barry

Read More Free Articles on This Site

There are over 450 pages of articles on this site with over 40 pages on database concepts and standards.

Search this site for more articles

Custom Search

Browse this site for more articles

Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current article: SQL-92.

Loading...

The Savvy Manager's Guide

Douglas K Barry has prepared the material on this site. He is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide

Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)

by with David Dick

One of the toughest jobs for managers today is keeping up with the rapid changes in technology. An important change in technology is that the future of software will involve service-oriented architectures with some form of cloud computing. More and more services are available on the Internet. Nearly every day, we can discover new opportunities to connect these services together to create service-oriented architectures (SOAs). These SOAs will require less custom software in organizations, but will likely demand more creativity in the selection and assembly of services. This is a natural evolution of software technology and will be explained in this book.

This is a non-technical book on a technical subject. It assumes no prior knowledge of the technology. It is written with a high-level view at the beginning of the book. As the book progresses, technical details are introduced and explained. You can stop reading at any point once you have enough understanding for your use.

"Web Services, Service-Oriented Architectures, and Cloud Computing by Douglas Barry provides easy-to-follow guidance around the proper use of web services, how they exist within SOA, and how the emerging use of cloud computing correctly fits into the mix. This is something that most in this industry can neither define nor implement, and getting it right the first time is critical to success. If you're looking to understand the true nature of web services, SOA, and cloud computing—including the underlying details—then you should begin by reading this book."


Author, Founder and CTO of Blue Mountain Labs