Re: materialized view vs. denormalized table
From: Rick Sawtell (ricksawtell_at_hotmail.com)
Date: 09/07/04
- Next message: pmattson: "RE: Storing Images"
- Previous message: Bob Castleman: "Re: removing a secondary log file?"
- In reply to: ChrisR: "materialized view vs. denormalized table"
- Next in thread: Wayne Snyder: "Re: materialized view vs. denormalized table"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 7 Sep 2004 12:56:45 -0700
A denormalized table is simply a table that doesn't follow the 3nf
standards. This happens a lot to improve efficiency of the queries at the
cost of storage space.
So a denormalized table may have duplicate columns, data or other items in
it that violate the normal forms.
A materialized view however is simply a view that has been created on a
table(s) that has then had a clustered index created for that view. SQL
Server stores the clustered index on the view. This can make queries much
faster. This is especially true in instances where there is a large amount
of calculations or aggregations going on in the query itself.
You do not have to repopulate the clustered index as data is modified in the
base tables. This happens automagically. =)
There is more to learn about this topic. Check out materialized views in
the Books Online.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"ChrisR" <anonymous@discussions.microsoft.com> wrote in message
news:799d01c49512$2e6bc060$a301280a@phx.gbl...
> sql2k sp3
>
> Whats the difference between these two? Isn't a
> materialized view nothing more than a denormalized table?
> Dont you need to update/ repopulate them both if data in
> the underlying table changes?
>
>
> TIA, ChrisR
- Next message: pmattson: "RE: Storing Images"
- Previous message: Bob Castleman: "Re: removing a secondary log file?"
- In reply to: ChrisR: "materialized view vs. denormalized table"
- Next in thread: Wayne Snyder: "Re: materialized view vs. denormalized table"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|