Using Materialized Views
A New/Old Tool For the Toolbelt
Issue: 10.4 (May/June 2012)
Author: Craig Boyd
Article Description: No description available.
Article Length (in bytes): 12,405
Starting Page Number: 35
RBD Number: 10412
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
One of the great things about being a software developer is all the cool tools we get to use and learn about. There are always new ones being created and then there are also some older ones that we wonder how it is that we have never heard of them.
In this article I am going to introduce a tool that has been around for a while and exists in some form on most DBMS (database management system) platforms. It is called a materialized view.
Setting the Stage
I need to set some boundaries before we get too far into this discussion. As we come across database terms that may be unclear to the reader I will define them in a general sort of way. The reason for this is because, while conceptually the terms can be used in the context of almost any DBMS, they are usually implemented in very different ways and can have profound impacts on how you design the physical structure of your database.
So let's step back for moment. When you run a SELECT statement, essentially what happens is that you get back a virtual table or result set. This result set is very short lived and takes up no space in the database. Additionally, it may or may not perform well depending on several factors such as available indexes, current workload of the server, the DBMS's query optimizer, etc. The need for the output is immediate and it is expected that the results will be current as of the point in time when the statement executed.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.