Home/ Questions/Q 3870494
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T21:43:59+00:00

Is it a good practice to query views instead of the raw tables in

  • 0

Is it a good practice to query views instead of the raw tables in stored procedures? (even if the view doesnt provide any different data)

I always figured it might be a good idea, because its an extra layer of abstraction and its similar to using properties instead of member variables in class functions.

But now I was looking at the stored procedures created by the ASP.NET Membership Provider and they always query against the tables directly.

I am aware that you cant insert data easily when using views, but if the stored procedure only queries data, should you still use tables directly? If yes, whats the main reason? (performance?)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A view is just a macro that expands into an outer query.

    If your view contains several joins, then when you join if to other views you suddenly have a 20 or 30 way JOIN when you actually see 3 JOINs in the SQL of the stored procedure. You’ll also find that each query is different: why keep joining the same 20 or 30 tables for every query?

    Generally, there is no benefit unless the view is indexed/materialised and the optimiser can use it.

    Ideas such as having calculations on a single table masked by a view should be in a computed column: why keep calculating it? For a calculation on multiple tables in a view, it should be indexed.

    Using a stored procedure already means no base table access (ownership chaining).

    There are good uses of views to avoid direct table access by users, or to mask schema changes, or provide some basic security (eg based on SUSER_SNAME), but not for performance or idealogy

    • 0