<?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: Using XML Data Types in Order System</title>
	<atom:link href="http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/</link>
	<description>Build world class ecommerce applications using Microsoft Commerce Server</description>
	<lastBuildDate>Fri, 06 Jan 2012 04:06:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: ravikanth</title>
		<link>http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/comment-page-1/#comment-219</link>
		<dc:creator>ravikanth</dc:creator>
		<pubDate>Fri, 15 May 2009 03:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/#comment-219</guid>
		<description>Arik, it depends on the data load you are having on the site. Ideally we archive old information to another server (may be 3  months old). In that context the order tables will not have not much information and a trigger will not cause any performance issue. If you are keeping all old information in the same table, this approach may create some performance issues in long run. That is the reason, I mentioned - &quot;The solution may or May not work for you&quot;.

Hope this helps.</description>
		<content:encoded><![CDATA[<p>Arik, it depends on the data load you are having on the site. Ideally we archive old information to another server (may be 3  months old). In that context the order tables will not have not much information and a trigger will not cause any performance issue. If you are keeping all old information in the same table, this approach may create some performance issues in long run. That is the reason, I mentioned &#8211; &#8220;The solution may or May not work for you&#8221;.</p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arik</title>
		<link>http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/comment-page-1/#comment-218</link>
		<dc:creator>arik</dc:creator>
		<pubDate>Thu, 14 May 2009 17:21:08 +0000</pubDate>
		<guid isPermaLink="false">http://microsoftblog.co.in/commerceserver/using-xml-data-types-in-order-system/#comment-218</guid>
		<description>Ravi ,
Have you ever tried using triggers on the order tables?
Won&#039;t i get performance issues ?

thanks
arik</description>
		<content:encoded><![CDATA[<p>Ravi ,<br />
Have you ever tried using triggers on the order tables?<br />
Won&#8217;t i get performance issues ?</p>
<p>thanks<br />
arik</p>
]]></content:encoded>
	</item>
</channel>
</rss>

