STRUCTURED QUERY LANGUAGE. A 'language' used with large and medium size DataBase applications to provide a more 'natural language' interface between human and system
SQL is implemented at many levels of database communication, from a simple Access form list box right up to high-volume communications between mainframes. SQL is widely implemented in almost every DBMS that supports SQL statements for communication. The reason for this level of acceptance is partially explained by the amount of effort that went into the theory and development of the standards.
The vast majority of the language has not changed through these updates. We can all profit from the fact that almost all of the code we wrote to SQL standards of 1989 is still perfectly usable. Or in other words, as a new student of SQL there is over ten years of SQL code out there that needs your expertise to maintain and expand.
Most DBMS are designed to meet the SQL92 standard.Since many of the advanced features of SQL92 have yet to be implemented by DBMS vendors, there has been little pressure for a new version of the standard. Nevertheless a SQL99 standard was developed to address advanced issues in SQL. All of the core functions of SQL, such as adding, reading and modifying data, are the same. As of early 2001, no vendor has implemented the SQL99 standard.
There are three areas where there is current development in SQL standards.
Flavors of SQL
The computer industry (like most industries) both benefits and suffers from standards. As said SQL is an open standard, not owned by a company, and the standard comes from ANSI and ISO. Therefore the SQL standard from ANSI/ISO is the "pure" SQL and called ANSI-SQL.
Problems emerge to frustrate this pureness:
First of all every DBMS vendor wants to differentiate their DBMS products. So if you look at the feature set of each DBMS product you see that not only does the product support ANSI-SQL but it also offers extra features, enhancements or extensions that are available only from individual vendors. For example, most vendors offer a field type which auto- increments even though this is not described in the SQL standards. These additions to ANSI-SQL are generally proprietary and will not work if you try to use them on competitor's SQL products.
Many of these features are powerful and robust, but since they vary from vendor to vendor, programmers should use them with caution. It is always safest to stick with pure SQL whenever possible.
Such enhancements are not all bad because these extensions are very
useful. For example, ANSI-SQL does not contain an automatic way to
assign a serial number to each new record but most DBMS sold today
have added this feature. Since serial numbering is so common programmers
are happy to have the enhancement. However, the method of implementation
is not uniform, so code written to get the serial number from data
in one DBMS may not work when used with another vendor's DBMS.
The father of relational databases, and thus SQL, is Dr. E.F. "Ted" Codd who worked for IBM. After Codd described a relational model for databases in 1970, IBM spent a lot of time and money researching how to implement his ideas.
IBM came to market with a product named System/R in 1978.
But other companies had formed and created relational database products before IBM was ready to release System/R.
The first to market was Relational Software's product named Oracle and the second was Relational Technology's Ingres.
IBM then released improved products named SQL/DS and DB2. Oracle and DB2 are still available today in nth generation forms while the Ingres technology was bought by Computer Associates.
The commercial acceptance of SQL was promoted by the formation of SQL Standards committees by the American National Standards Institute and the International Standard Organization.
The ISO AND ansi publish a specification known as SQL-89.
An improved version SQL-92 appears adding some 600 pages to the descriotion of the 1989 standard.
The third generation is published as SQL-99
|Last Updated on April 25, 2004||For suggestions please mail the editors|
Footnotes & References
|1||Copyright © 2000 by The TRAC Foundation, Inc. republished courtesy of the TRAC foundation.|
|2||TRAC is a trademark of the TRAC Foundation, Inc.|
|3||part of the text is adapter from: www.vbip.com/books/1861001800/chapter_1800_02.asp|