<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: difference between materialized views and tables</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 01:14:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: ammalu</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-103052</link>
		<dc:creator>ammalu</dc:creator>
		<pubDate>Fri, 17 Feb 2012 16:31:58 +0000</pubDate>
		<guid isPermaLink="false">#comment-103052</guid>
		<description><![CDATA[but we cant do any changes on mv because dml not allowed on mv................]]></description>
		<content:encoded><![CDATA[<p>but we cant do any changes on mv because dml not allowed on mv&#8230;&#8230;&#8230;&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mohankumar</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-38199</link>
		<dc:creator>mohankumar</dc:creator>
		<pubDate>Tue, 27 Dec 2005 11:29:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-38199</guid>
		<description><![CDATA[
As the name itself says it gives you all the added advantages of views over table, like selective data sharing. You can build a MV based on many base tables without changing your DB arichiecture using joins.
MV are more usefull for precomputed data store for datawarehouse purposes.
]]></description>
		<content:encoded><![CDATA[<p>As the name itself says it gives you all the added advantages of views over table, like selective data sharing. You can build a MV based on many base tables without changing your DB arichiecture using joins.<br />
MV are more usefull for precomputed data store for datawarehouse purposes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pelaez</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-38200</link>
		<dc:creator>pelaez</dc:creator>
		<pubDate>Wed, 21 Dec 2005 12:00:30 +0000</pubDate>
		<guid isPermaLink="false">#comment-38200</guid>
		<description><![CDATA[I agree with Mr. Oracle

Query rewrite is a great advantage of MVs.

If you define a materialized view, the optimizer will decide for each query (even those written before the MV) whether using the MV or the underlying tables is the most effective execution plan.

MVs might not be very useful in transactional systems, which get updated all the time, but are handy in business intelligence environments.]]></description>
		<content:encoded><![CDATA[<p>I agree with Mr. Oracle</p>
<p>Query rewrite is a great advantage of MVs.</p>
<p>If you define a materialized view, the optimizer will decide for each query (even those written before the MV) whether using the MV or the underlying tables is the most effective execution plan.</p>
<p>MVs might not be very useful in transactional systems, which get updated all the time, but are handy in business intelligence environments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mroracle</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-38201</link>
		<dc:creator>mroracle</dc:creator>
		<pubDate>Wed, 21 Dec 2005 11:46:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-38201</guid>
		<description><![CDATA[The real benefit to MVs is the query rewrite feature...  If you have that feature enabled, it will take queries that COULD be using the materialized view instead of what they wrote - and rewrite them BEFORE they get executed!!!

The other advantage as someone else said is the built in mechanisms to keep it updated rather than writing all that yourself.

I hope this helps.

((MrO))
]]></description>
		<content:encoded><![CDATA[<p>The real benefit to MVs is the query rewrite feature&#8230;  If you have that feature enabled, it will take queries that COULD be using the materialized view instead of what they wrote &#8211; and rewrite them BEFORE they get executed!!!</p>
<p>The other advantage as someone else said is the built in mechanisms to keep it updated rather than writing all that yourself.</p>
<p>I hope this helps.</p>
<p>((MrO))</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cassidy6o6</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-38202</link>
		<dc:creator>cassidy6o6</dc:creator>
		<pubDate>Wed, 21 Dec 2005 11:37:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-38202</guid>
		<description><![CDATA[Hi,

Thanks for your reply. Can I say that the materialized view got the advantage for saving time to write the script to reflash the data as Oracle has written a pl/sql script to handle the refresh. Other than that there is not much difference? If I am willing to write those scripts to update the changes on my table. There is not much difference? Will there be any advantages on materialized views other than tables beside the refreshing?

Cassidy]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for your reply. Can I say that the materialized view got the advantage for saving time to write the script to reflash the data as Oracle has written a pl/sql script to handle the refresh. Other than that there is not much difference? If I am willing to write those scripts to update the changes on my table. There is not much difference? Will there be any advantages on materialized views other than tables beside the refreshing?</p>
<p>Cassidy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: enkidu</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/difference-between-materialized-views-and-tables/#comment-38203</link>
		<dc:creator>enkidu</dc:creator>
		<pubDate>Wed, 21 Dec 2005 02:52:39 +0000</pubDate>
		<guid isPermaLink="false">#comment-38203</guid>
		<description><![CDATA[Hi,

also you do not need any program to refresh the snap-shot tables (mv) There&#039;re built-in pl/sql packages to refresh these types of tables. You can specify a time interval for refresh, even you can define on-commit snap-shots.

regards]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>also you do not need any program to refresh the snap-shot tables (mv) There&#8217;re built-in pl/sql packages to refresh these types of tables. You can specify a time interval for refresh, even you can define on-commit snap-shots.</p>
<p>regards</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.052 seconds using memcached
Object Caching 337/343 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-19 02:20:25 -->