I have used MSSQL Server for 10 years.
I just have used Tables(obvious), Diagrams an Stored Procedures.
Yesterday I learn how to use UDF, they are easy.
Now I want to use Views.
I have an idea(logical) how they work, but I want to ask some questions to
begin with:

1. When you CREATE a VIEW, information in it is not UPDATED automatically if
TABLES related with are UPDATED, it means, VIEWS are independent from TABLES.

2. If information in VIEWS is temporary, correct use of them is.
a) CREATE it.
b) USE it inmediately
c) CLEAR it or DROP it.

3. If all my work is done in SP's, a good way to use VIEWS is to CREATE, to
USE and to DROP inside SP's.

Beforehand, thank you very much.

Actually, quite the opposite is true. A view does not store any
information; it is simply a saved copy of the query. When you say SELECT
col_list FROM dbo.view_name; SQL Server actually goes out and fetches the
data from the table (assuming the view references a table; you can create a
view that doesn't, but this is rather rare).

Well, there is an exception: indexed views. An indexed view actually does
save a copy of the data, but it is automatically updated when you update the
base table(s).

In both cases, the data "in the view" is always up to date.

I think you are thinking of #temp tables here, not views.

A view is simply a query over the table(s) so any modifications will be
immediately reflected in the base table(s). There are restrictions on
updateable views, however. see the Books Online for details.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"LUIS" discussions.microsoft.com> wrote in message
news:988E4CB2-9BED-4CE8-ACD2-131F951FFA85@microsoft.com...

Dan:

Thank you very much. By the way, your last name tells Spanish roots. Es es
bueno.

--
Luis Garcia
IT Consultant

"Dan Guzman" wrote:

Aaron

Thank you very much. You avoid to me the biggest misunderstanding that I do
for living.

--
Luis Garcia
IT Consultant

"Aaron Bertrand [SQL Server MVP]" wrote: