Introduction to Indexed Views in SQL Server
This article explains indexed views and provides an example that shows when they should be used to improve performance of a complex query.
2020-02-25
21,916 reads
Indexed Views
SQL Server Indexed Views: The Basics
Views are a valuable tool for the SQL Server Developer, because they hide complexity and allow for a readable style of SQL expression. They aren't there for reasons of performance, and so indexed views are designed to remedy this shortcoming. They're great in certain circumstances but they represent a trade-off, and they come with considerable 'small print'. Jes Borland explains.
2014-02-26
4,674 reads
If you are using indexed views and MERGE, please read this!
Here is some information about an important MERGE “wrong results” bug, involving indexed views, that could be affecting the accuracy of your queries right now, and what options you have for working around the problem.
2013-02-14
4,584 reads
SQL Server Indexed Views
Views can be an effective tool for speeding up your selects and simplifying complex queries. Learn what indexed views are, where you might want to use them, how to create them, and what constraints exist with their use.
2010-04-05
5,000 reads
2009-06-09
3,966 reads
2008-09-09
12,788 reads
Blogs
In-Person CISA Training – April 13-16, 2026
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB 2026
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
The FinOps Lifecycle: From Budgeting to Reporting
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Forums
VS Code, Unresolved References.
Hi all, I just started using VS Code to work with DB projects. I...
Fun with JSON II
Comments posted to this topic are about the item Fun with JSON II
Changing Data Types
Comments posted to this topic are about the item Changing Data Types
Question of the Day
Fun with JSON II
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers