Vous êtes sur la page 1sur 5


AI M- I ntroduction to SQL And installation of Oracle
Introduction to SQL:
The Structured Query Language (SQL) is the language of databases. The relational model was first proposed by
E.F.Codd in 1970. D. D. Chamberlin and others at the IBM San Jose Research Laboratory developed a language
now called SQL, or Structured Query Language, as a data sublanguage for the relational model.
Originally spelled SEQUEL, the language was presented in a series of papers starting in 1974, and it
was used in a prototype relational system called System R, which was developed by IBM in the late 1970s.
Other early prototype relational database management systems included INGRES, which was developed at the
University of California at Berkeley, and the Peterlee Relational Test Vehicle, developed at the IBM UK
Scientific Laboratory. System R was evaluated and refined over a period of several years, and it became the
basis for IBMs first commercially available relational database management system, SQL/DS, which was
announced in 1981.
Another early commercial database management system, Oracle, was developed in the late 1970s using
SQL as its language. IBMs DB2, also using SQL as its language, was released in 1983. Microsoft SQL Server,
MySQL, Informix, Sybase, dBase, Paradox, r: Base, FoxPro, and hundreds of other relational database
management systems have incorporated SQL.
Both the American National Standards Institute (ANSI) and the International Standards Organization
(ISO) adopted SQL as a standard language for relational databases and published specifications for the SQL
language in 1986. This standard is usually called SQL1.
A minor revision, called SQL-89, was published three years later. A major revision, SQL2, was adopted
by both ANSI and ISO in 1992. The first parts of the SQL3 standard, referred to as SQL: 1999, were published
in 1999. Major new features included object-oriented data management capabilities and user-defined data types.
Most vendors of relational database management systems use their own extensions of the language, creating a
variety of dialects around the standard.
SQL has a complete data definition language (DDL) and data manipulation language (DML) described
in this chapter, and an authorization language, described in Chapter 9. Readers should note that different
implementations of SQL vary slightly from the standard syntax presented here, but the basic notions are the
The Structured Query Language (SQL) is the language of databases. All modern relational databases,
including Access, FileMaker Pro, Microsoft SQL Server and Oracle use SQL as their basic building block. In
fact, its often the only way that you can truly interact with the database itself. All of the fancy graphical user
interfaces that provide data entry and manipulation functionality are nothing more than SQL translators.
They take the actions you perform graphically and convert them to SQL commands understood by the
SQL stands for Structured Query Language
SQL lets you access and manipulate databases
SQL is an ANSI (American National Standards Institute) standard

1. AlwaysOn Availability Groups -- This feature takes database mirroring to a whole new level. With
AlwaysOn, users will be able to fail over multiple databases in groups instead of individually.
Also, secondary copies will be readable, and can be used for database backups. The big win is that your DR
environment no longer needs to sit idle.
2. Windows Server Core Support -- If you don't know what Windows Server Core is, you may want to come
up to speed before Windows 8 (MS is making a push back to the command line for server products). Core is the
GUI-fewer versions of Windows that uses DOS and PowerShell for user interaction.
It has a much lower footprint (50% less memory and disk space utilization), requires fewer patches, and
is more secure than the full install. Starting with SQL 2012, it is supported for SQL Server.
3. Columnstore Indexes -- This is a cool new feature that is completely unique to SQL Server. They are special
type of read-only index designed to be use with Data Warehouse queries.
Basically, data is grouped and stored in a flat, compressed column index, greatly reducing I/O and
memory utilization on large queries.
4. User-Defined Server Roles -- DBAs have always had the ability to create custom database role, but never
server wide. For example, if the DBA wanted to give a development team read/write access to every database
on a shared server, traditionally the only ways to do it were either manually, or using undocumented procedures.
Neither of which were good solutions. Now, the DBA can create a role, which has read/write access on every
DB on the server, or any other custom server wide role.
5. Enhanced Auditing Features -- Audit is now available in all editions of SQL Server. Additionally, users can
define custom audit specifications to write custom events into the audit log. New filtering features give greater
flexibility in choosing which events to write to the log.
6. BI Semantic Model -- This is replacing the Analysis Services Unified Dimensional Model (or cubes most
people referred to them). It's a hybrid model that allows one data model will support all BI experiences in SQL
Server. Additionally, this will allow for some really neat text info graphics.
7. Sequence Objects -- For those folks who have worked with Oracle, this has been a long requested feature. A
sequence is just an object that is a counter -- a good example of it's use would be to increment values in a table,
based a trigger.
SQL has always had similar functionality with identity columns, but now this is a discrete object.
8. Enhanced PowerShell Support -- Windows and SQL Server admins should definitely start brushing up on
their PowerShell scripting skills. Microsoft is driving a lot of development effort into instrumenting all of their
server-based products with PowerShell.
SQL 2008 gave DBAs some exposure to it, but there are many more in cmdlets in SQL 2012.
9. Distributed Replay -- Once again this is answer to a feature that Oracle released (Real Application Testing).
However, and in my opinion where the real value proposition of SQL Server is, in Oracle it is a (very
expensive) cost option to Enterprise Edition. With SQL, when you buy your licenses for Enterprise Edition, you
get everything.
Distributed replay allows you to capture a workload on a production server, and replay it on another machine.
This way changes in underlying schemas, support packs, or hardware changes can be tested under production
10. PowerView -- You may have heard of this under the name "Project Crescent" it is a fairly powerful self-
service BI toolkit that allows users to create mash ups of BI reports from all over the Enterprise.
11. SQL Azure Enhancements -- These don't really go directly with the release of SQL 2012, but Microsoft is
making some key enhancements to SQL Azure. Reporting Services for Azure will be available, along with
backup to the Windows Azure data store, which is a huge enhancement.
The maximum size of an Azure database is now up to 150G. Also Azure data sync allows a better hybrid model
of cloud and on-premise solutions.
12. Big Data Support -- I saved the biggest for last, introduced at the PASS (Professional Association for SQL
Server) conference last year, Microsoft announced a partnership with Hadoop provider Cloudera.
One part of this involves MS releasing a ODBC driver for SQL Server that will run on a Linux platform.
Additionally, Microsoft is building connectors for Hadoop, which is an extremely popular NoSQL platform.
With this announcement, Microsoft has made a clear move into this very rapidly growing space.
SQL 2012 is a big step forward for Microsoft -- the company is positioning itself to be a leader in availability
and in the growing area of big data. As a database professional, I look forward to using SQL 2012 to bring new
solutions to my clients.
What Can SQL do?
SQL can execute queries against a database
SQL can retrieve data from a database
SQL can insert records in a database
SQL can update records in a database
SQL can delete records from a database
SQL can create new databases
SQL can create new tables in a database
SQL can create stored procedures in a database
SQL can create views in a database
SQL can set permissions on tables, procedures, and views

SQL commands are divided into five categories:
1. DDL
2. DML
3. DCL
4. TCL
5. DQL

1. DDL - Data Definition Language:
DDL statements are used to define the database structure or schema. SQL commands which comes under Data
Definition Language (DDL) are :
CREATE To create objects in the database
ALTER Alters the structure of the database
DROP Delete objects from the database
TRUNCATE Remove all records from a table, also free the space occupied by those records

2. DML Data Manipulation Language:
DML statements are used for managing data within schema objects. SQL commands which comes under Data
Manipulation Language (DML) are :
INSERT Insert data into a table
UPDATE Updates existing data within a table
DELETE Deletes all records from a table, the space occupied will remain

3. DCL Data Control Language:
DCL statements are used to control access to the data and to the database.
GRANT Gives users access privileges to database.
REVOKE Withdraw access privileges given with the GRANT command.

4. TCL Transaction Control:
TCL statements are used to manage the changes made by DML statements. It allows statements to be grouped
together into logical transactions.
COMMIT save the work done.
SAVEPOINT it marks a point in a transaction to which you can roll back.
ROLLBACK restore database to original since the last COMMIT or SAVEPOINT

5. DQL Data Query Language
It includes SELECT statement. Using it one can query in database.
SELECT It display the records from table.