﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Teradata Forums / Data Warehousing  / Teradata   / Data Skew on a UPI table (with HIGH volume) - How? / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Teradata Forums</description><link>http://www.teradata.com/teradataforum/</link><webMaster>info@teradata.com</webMaster><lastBuildDate>Wed, 03 Dec 2008 18:36:57 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Data Skew on a UPI table (with HIGH volume) - How?</title><link>http://www.teradata.com/teradataforum/Topic11104-1-1.aspx</link><description>Thank you, Dieter! That was pretty good information. I never would have thought 9MM rows was not enough volume. :-)We've more than 1 day's data in those tables now and we're seeing much better numbers (distribution). </description><pubDate>Tue, 08 Apr 2008 14:15:27 GMT</pubDate><dc:creator>SayeeRamPrasad</dc:creator></item><item><title>RE: Data Skew on a UPI table (with HIGH volume) - How?</title><link>http://www.teradata.com/teradataforum/Topic11104-1-1.aspx</link><description>Hi Sayee,most of the skew is due to the high number of AMPs:There are 65536 entries within the hashmap, so the average number of entries per AMP is:SELECT 2**16/1400  -&amp;gt;  46,81Of course there's no .81 entry, so some AMPs will get 46 and some 47:SELECT 47/46.0000  -&amp;gt;  1,0217  -&amp;gt; 2.17 percent more data even if there's a UPI.Now the table is still small (for a 1400 AMP system), 6642 rows per AMP in average, this is probably not enough for a perfectly even distribution. Now add this small skew to the 2.17 percent...Dieter</description><pubDate>Tue, 01 Apr 2008 08:49:26 GMT</pubDate><dc:creator>dnoeth</dc:creator></item><item><title>Data Skew on a UPI table (with HIGH volume) - How?</title><link>http://www.teradata.com/teradataforum/Topic11104-1-1.aspx</link><description>We've a SET table defined with a UPI that has 9.3 Million rows on a 1400 AMP,  V2R6 Teradata system. Please look at the numbers below. The AMP that has the MAX rows has 3.47 times more rows than the AMP with the MIN rows. This does not make sense to me given the fact that we've a UPI and a high volume of rows in the table for an even distribution.xTimesGreaterMaxAvg - 1.56xTimesGreaterMaxMin - 3.47Mx - 1393664Avrg - 890657.07Mn - 401920CurPerm - 1282546176Can someone please shed some light on this? Is there something we can look at to improve data distribution? Any help would be greatly appreciated.PS: The table also has a PPI defined on a date field which is part of the UPI (if this matters).Thanks,Sayee.</description><pubDate>Mon, 31 Mar 2008 19:08:41 GMT</pubDate><dc:creator>SayeeRamPrasad</dc:creator></item></channel></rss>