SQL Server BasicsWhat is SQL Server database?What is RDBMS?What is Normalization?Why we use Denormalization?What_is_SQL?What is PL/SQL?Difference between SQL and PL/SQLDatabase TableOne to One RelationshipOne to Many RelationshipMany to Many RelationshipMany to One RelationshipString Data TypesNumber Data TypesDate Data TypesOther Data TypesCreate DatabaseDrop DatabaseCreating and Managing Users in SQL ServerCreate TableAlter TableDrop TableConstraints in SQL serverPrimary KeyForeign KeyUnique KeyCandidate KeyComposite KeyDifference between primary key and candidate keyPrimary key and foreign key relationshipSurrogate KeyCascading Referential Integrity ConstraintsSelf Referential Integrity ConstraintsInsert into statementInsert multiple recordsUpdate statementDelete statementTruncate statementDifference between Delete and TruncateAlias in SQL ServerSelect statementSelect DistinctSelect TopSelect IntoNull Functions(ISNULL(),NULLIF(),COALESCE())Sub QueryIdentity ColumnSequence objectDifference between sequence and identity columnSQL Server ClausesWHERE ClauseOrder By ClauseTop N ClauseGroup By ClauseHaving ClauseDifference between Where and HavingSQL Server OperatorsArithmetic OperatorsComparison OperatorsLogical OperatorsBitwise OperatorsAny OperatorsAll OperatorsUnion OperatorsUnion All OperatorsDifference between Union and Union AllIntersect OperatorExcept OperatorDifference between Except and IntersectJoinsInner JoinLeft JoinRight JoinFull JoinSelf JoinCross JoinViewsWhat are views?Create views using SSMSIndexed ViewsComplex ViewsCheck Option in ViewCheck Encryption in ViewSchema Binding Option in ViewRead-only ViewsUpdatable ViewsAdvantages and disadvantages of viewsCreate multiple views on one tableCan we implement index on views?Can we Perform Insert, update, delete operation on views?Stored Procedure and FunctionsWhat are Stored Procedures?Why we use stored procedures?Passing parameters to Stored procedureUser-Defined FunctionsDifference between UDF and Stored procedurePre-Defined Functions@@Indentity and Scope_IndentityNULLIF, ISNULL and COALESCE
Previous
Next

Read-Only views in SQL Server.

In SQL Server, you can create a read-only view by using the WITH SCHEMABINDING option when creating the view. This option ensures that the underlying schema of the view cannot be modified while the view exists. Here's an example of creating a read-only view: 


-- Create a table
CREATE TABLE Employees (
    EmployeeID INT PRIMARY KEY,
    FirstName VARCHAR(50),
    LastName VARCHAR(50),
    Department VARCHAR(50)
);

-- Insert some sample data
INSERT INTO Employees (EmployeeID, FirstName, LastName, Department)
VALUES (1, 'John', 'Doe', 'Sales'),
       (2, 'Jane', 'Smith', 'Marketing'),
       (3, 'Bob', 'Johnson', 'IT');

-- Create a read-only view
CREATE VIEW ReadOnlyEmployees
WITH SCHEMABINDING
AS
SELECT EmployeeID, FirstName, LastName, Department
FROM Employees;

-- Attempting to modify the view will result in an error
-- For example, the following update statement will fail:
UPDATE ReadOnlyEmployees
SET Department = 'HR';

In this example, the ReadOnlyEmployees view is created with the WITH SCHEMABINDING option. This ensures that the view cannot be modified directly, preventing updates, inserts, or deletes on the view. Attempting to modify the view will result in an error.

Read-only views provide the following benefits:

  1. Controlled Access: Read-only views allow you to control and limit the data that users or applications can access. You can define the view's SELECT statement to include specific columns or apply filters to restrict the returned data.
  2. Data Protection: By preventing modifications through the view, read-only views help protect the integrity and consistency of the underlying data. They act as a safeguard against accidental or unauthorized changes.
  3. Simplified Queries: Read-only views can simplify the querying process for users by providing a pre-defined and filtered representation of the data. Users can query the view directly without worrying about complex JOINs or filtering conditions.

It's important to note that read-only views are based on the underlying tables, and any changes made to the tables will be reflected in the view. However, modifications made to the view itself will not affect the underlying tables.

Read-only views are particularly useful when you want to provide read-only access to specific subsets of data, such as creating simplified reports or exposing data to external applications while ensuring data integrity and security.

Previous
Next