---
title: "Difference between VIEW vs TABLE."  
description: "Difference between VIEW vs TABLE."  
author: "Anubhav Sharma"  
published: 2026-04-29  
updated: 2026-04-29  
canonical: https://www.mindstick.com/interview/34497/difference-between-view-vs-table  
category: "database"  
tags: ["database", "sql server"]  
reading_time: 3 minutes  

---

# Difference between VIEW vs TABLE.

### TABLE

- A **physical object** that stores actual data in the database
- Data is **persisted on disk**
- Supports **INSERT, UPDATE, DELETE**
- Can have indexes, constraints, keys

## Example:

```plaintext
CREATE TABLE Employees (
    Id INT PRIMARY KEY,
    Name VARCHAR(100),
    Salary DECIMAL(10,2)
);
```

### VIEW

- A **virtual table** based on a SQL query
- Does **not store data** (stores only the query)
- Data is fetched **dynamically from underlying tables**
- Mostly used for **security, abstraction, and reuse**

## Example:

```plaintext
CREATE VIEW EmployeeView AS
SELECT Name, Salary
FROM Employees;
```

## Key Differences

| Feature | TABLE | VIEW |
| --- | --- | --- |
| Storage | Stores data physically | No physical data storage |
| Type | Real object | Virtual object |
| Data Source | Direct | From one/more tables |
| DML Support | Full (Insert/Update/Delete) | Limited (depends on view) |
| Performance | Faster (direct access) | Slower (query execution) |
| Use Case | Data storage | Data abstraction/security |

## Simple Analogy

- **TABLE** → Like a **database file (actual data)**
- **VIEW** → Like a **saved query/report**

## When to Use

Use **TABLE** when:

- You need to store data
- Perform CRUD operations

Use **VIEW** when:

- You want to **simplify complex queries**
- Restrict access to specific columns
- Combine multiple tables into one logical view

## Final Thought

- **TABLE = Data Storage**
- **VIEW = Data Representation**

## Answers

### Answer by Anubhav Sharma

### TABLE

- A **physical object** that stores actual data in the database
- Data is **persisted on disk**
- Supports **INSERT, UPDATE, DELETE**
- Can have indexes, constraints, keys

## Example:

```plaintext
CREATE TABLE Employees (
    Id INT PRIMARY KEY,
    Name VARCHAR(100),
    Salary DECIMAL(10,2)
);
```

### VIEW

- A **virtual table** based on a SQL query
- Does **not store data** (stores only the query)
- Data is fetched **dynamically from underlying tables**
- Mostly used for **security, abstraction, and reuse**

## Example:

```plaintext
CREATE VIEW EmployeeView AS
SELECT Name, Salary
FROM Employees;
```

## Key Differences

| Feature | TABLE | VIEW |
| --- | --- | --- |
| Storage | Stores data physically | No physical data storage |
| Type | Real object | Virtual object |
| Data Source | Direct | From one/more tables |
| DML Support | Full (Insert/Update/Delete) | Limited (depends on view) |
| Performance | Faster (direct access) | Slower (query execution) |
| Use Case | Data storage | Data abstraction/security |

## Simple Analogy

- **TABLE** → Like a **database file (actual data)**
- **VIEW** → Like a **saved query/report**

## When to Use

Use **TABLE** when:

- You need to store data
- Perform CRUD operations

Use **VIEW** when:

- You want to **simplify complex queries**
- Restrict access to specific columns
- Combine multiple tables into one logical view

## Final Thought

- **TABLE = Data Storage**
- **VIEW = Data Representation**


---

Original Source: https://www.mindstick.com/interview/34497/difference-between-view-vs-table

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.