Views

The syntax used to create views in Microsoft SQL Server is similar to that of Oracle.

Oracle	Microsoft SQL Server
CREATE [OR REPLACE] [FORCE \| NOFORCE] VIEW [schema.]view_name [(column_name [, column_name]...)] AS select_statement [WITH CHECK OPTION [CONSTRAINT name]] [WITH READ ONLY]	CREATE VIEW [owner.]view_name [(column_name [, column_name]...)] [WITH ENCRYPTION] AS select_statement [WITH CHECK OPTION]

SQL Server views require that the tables exist and that the view owner has privileges to access the requested tables(s) specified in the SELECT statement (similar to the Oracle FORCE option).

By default, data modification statements on views are not checked to determine whether the rows affected are within the scope of the view. To check all modifications, use the WITH CHECK OPTION. The primary difference between the WITH CHECK OPTION is that Oracle defines it as a constraint, while SQL Server does not. Otherwise, it functions the same in both.

Oracle provides a WITH READ ONLY option when defining views. SQL Server applications can achieve the same result by granting only SELECT permission to the users of the view.

Both SQL Server and Oracle views support derived columns, using arithmetic expressions, functions, and constant expressions. Some of the specific SQL Server differences are:

Data modification statements (INSERT or UPDATE) are allowed on multitable views if the data modification statement affects only one base table. Data modification statements cannot be used on more than one table in a single statement.
READTEXT or WRITETEXT cannot be used on text or image columns in views.
ORDER BY, COMPUTE, FOR BROWSE, or COMPUTE BY clauses cannot be used.
The INTO keyword cannot be used in a view.

When a view is defined with an outer join and is queried with a qualification on a column from the inner table of the outer join, the results from SQL Server and Oracle can differ. In most cases, Oracle views are easily translated into SQL Server views.

Oracle	Microsoft SQL Server
CREATE VIEW STUDENT_ADMIN.STUDENT_GPA (SSN, GPA) AS SELECT SSN, ROUND(AVG(DECODE(grade ,'A', 4 ,'A+', 4.3 ,'A-', 3.7 ,'B', 3 ,'B+', 3.3 ,'B-', 2.7 ,'C', 2 ,'C+', 2.3 ,'C-', 1.7 ,'D', 1 ,'D+', 1.3 ,'D-', 0.7 ,0)),2) FROM STUDENT_ADMIN.GRADE GROUP BY SSN	CREATE VIEW STUDENT_ADMIN.STUDENT_GPA (SSN, GPA) AS SELECT SSN, ROUND(AVG(CASE grade WHEN 'A' THEN 4 WHEN 'A+' THEN 4.3 WHEN 'A-' THEN 3.7 WHEN 'B' THEN 3 WHEN 'B+' THEN 3.3 WHEN 'B-' THEN 2.7 WHEN 'C' THEN 2 WHEN 'C+' THEN 2.3 WHEN 'C-' THEN 1.7 WHEN 'D' THEN 1 WHEN 'D+' THEN 1.3 WHEN 'D-' THEN 0.7 ELSE 0 END),2) FROM STUDENT_ADMIN.GRADE GROUP BY SSN

Oracle

Microsoft SQL Server

CREATE VIEW STUDENT_ADMIN.STUDENT_GPA
(SSN, GPA)
AS SELECT SSN,    ROUND(AVG(DECODE(grade
                        ,'A', 4
                        ,'A+', 4.3
                        ,'A-', 3.7
                        ,'B', 3
                        ,'B+', 3.3
                        ,'B-', 2.7
                        ,'C', 2
                        ,'C+', 2.3
                        ,'C-', 1.7
                        ,'D', 1
                        ,'D+', 1.3
                        ,'D-', 0.7
                        ,0)),2)
FROM STUDENT_ADMIN.GRADE
GROUP BY SSN

CREATE VIEW STUDENT_ADMIN.STUDENT_GPA
(SSN, GPA)
AS SELECT SSN, ROUND(AVG(CASE grade
                    WHEN 'A' THEN 4
                    WHEN 'A+' THEN 4.3
                    WHEN 'A-' THEN 3.7
                    WHEN 'B' THEN 3
                    WHEN 'B+' THEN 3.3
                    WHEN 'B-' THEN 2.7
                    WHEN 'C' THEN 2
                    WHEN 'C+' THEN 2.3
                    WHEN 'C-' THEN 1.7
                    WHEN 'D' THEN 1
                    WHEN 'D+' THEN 1.3
                    WHEN 'D-' THEN 0.7
                    ELSE 0
                    END),2)
FROM STUDENT_ADMIN.GRADE
GROUP BY SSN