Comments on: SQL View performance vs. SELECT

By: kccrosser

kccrosser — Fri, 15 May 2009 16:13:09 +0000

(Reposting to try to fix bad link ref) You could try using an Indexed View. There is a good simple overview of these at: Intro to Indexed Views Basically, if your view doesn’t violate any of the limitations of an indexed view, this allows creating a view that can have physical indexes applied to it, so you can tune performance much better than with a non-indexed view.

By: kccrosser

kccrosser — Fri, 15 May 2009 16:11:19 +0000

You could try using an Indexed View. There is a good simple overview of these at: http://www.sqlteam.com/article/indexed-views-in-sql-server-2000 Basically, if your view doesn't violate any of the limitations of an indexed view, this allows creating a view that can have physical indexes applied to it, so you can tune performance much better than with a non-indexed view.

By: koverton44

koverton44 — Thu, 14 May 2009 21:12:47 +0000

That would also be true of a table query.

By: dmenke38

dmenke38 — Wed, 18 Mar 2009 13:43:24 +0000

A view that is derived from a table that is updated frequently will re-execute the underlying queries nearly every time it is accessed. The view actually creates a temporary result table in the database that is cached until an underlying query is stale (a table specified in the query is updated.)
If no changes occur, the cached table is returned directly, otherwise the underlying queries is re-executed, a slower process.