The Origins of SQL IBM created (Geocities web hosting) the original
The Origins of SQL IBM created the original relational database technology. SQL was created as an uncomplicated, non-procedural way of accessing data from an IBM-created relational database. SQL was initially called Sequel. Thus, SQL is often pronounced as sequel. For some other databases, SQL is pronounced by representing each letter, as in ess-queue-ell. The meaning of the two pronunciations is identical. The query language used to access an object database is called Object Database Query Language (ODQL). The acronym QL thus means query language, a language used to query a database. In its most primitive form, SQL stems from the idea of a reporting language, devised in theory by the inventor of the relational database model. The roots of SQL lie in retrieval of sets of data. What this means is that SQL is intended as a language to retrieve many records from one or many tables at once, yielding a result set. SQL was not originally intended to retrieve individual records from a relational database, as exact record matches, common in transactional and OLTP databases. However, SQL can now be used to do precisely just that, and with excellent efficiency. SQL is now used in modern-day relational database engines to retrieve both sets of records, and individual records, in transactional, OLTP, and data warehouse databases. What does all this mean without using a plethora of nasty long words? In short, SQL was developed as a shorthand method of retrieving information from relational databases. SQL has become the industry standard over the last 20 years. The following is an example of a query (a request or question put to the database) written in SQL, in this case all the records in the AUTHOR table will be retrieved: SELECT AUTHOR_ID, NAME FROM AUTHOR; AUTHOR_ID NAME ———- ——————————– 1 Orson Scott Card 2 James Blish 3 Isaac Azimov 4 Larry Niven 5 Jerry Pournelle 6 William Shakespeare 7 Kurt Vonnegut SQL for Different Databases SQL as implemented in different database engines is not standardized. Each database vendor developed a unique relational database, and relational database management system (database management toolkit). The result was different relational databases having different strengths. The vendors often altered and extended the standard form of SQL to take advantage of the way in which their individual products were written. The result is that relational database products from different vendors, although similar in nature, and even appearance, are often very different internally. Additionally, the different relational databases are different both in internal structural characteristics, and in the way they are used. And that s only the database engine itself. There is also use of different computer hardware platforms and operating systems. The larger database vendors service multiple operating systems, with completely different versions of the database software, applicable to different operating systems, even down to different flavors of Unix. 125 Reading and Writing Data with SQL
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.