Topics Topics Help/Instructions Help Edit Profile Profile Member List Register Paatha Gnyapakaalu - Archives from Old DB  
Search New Posts 1 | 2 | 8 Hours Search New Posts 1 | 3 | 7 Days Search Search Tree View Tree View Latest tweets Live Tweets   Hide Images

Rate this post by selecting a number. 1 is the worst and 5 is the best.

    (Worst)    1    2    3    4    5     (Best)

Author Message
Top of pagePrevious messageNext messageBottom of page Link to this message

Onlyniru3
Censor Bewarse
Username: Onlyniru3

Post Number: 18251
Registered: 08-2009
Posted From: 216.105.250.49

Rating: N/A
Votes: 0

Posted on Friday, January 03, 2014 - 12:48 pm:   


Ferrari:

development lo oka 10k rows source file tho 5million rows unna lookup table tho join chesthe 40 minutes daaka pattindi...ade cached lookup tho ayithe less than 2 minutes tho ayipoyindi..nenu lookup table lo nunchi just 4 columns ee testhunnaanu...prod lo simple select statement(select col1 from tab1 where col2='xyz') run chesina kooda 1 min paduthondi....lookup table lo 500 mil rows unna naaku use ayyevi around 70 million untayi..na lookup override query will get these 70 million rows..even in this case also left outer join ee better antaavaa?




Go with lookup only then... Asalu inka problem em vundhi... Peformance baagundhi kadha... It all depends on the data types, Precision and scale of look up ports... One more thing you need to look for is, in future if the lookup table gets excessive in Size, the lookup cache might eat all the space on server...You need to keep an eye on that too...
Green Bay Packers... San Antonio Spurs... LSU Tigers...

Topics | Last Hour | Last Day | Last Week | Tree View | Search | Help/Instructions | Program Credits Administration