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
22,309 reads
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
22,309 reads
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
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
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,991 reads
2008-09-09
12,828 reads
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
By Arun Sirpal
“What exactly did it do on my server?” is the first question a DBA...
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
Comments posted to this topic are about the item Let's Talk Certifications
Comments posted to this topic are about the item The Hidden Security Risks of...
Comments posted to this topic are about the item The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers