Pandu_age40 Posted September 8, 2014 Report Posted September 8, 2014 Hello guys Tsql query okati long running unte how to reduce the time by increasing the performance ... I have seen many links but emana standard book or exclusively sql tuning medha with examples tho any links or books... Please help .. I appreciate your help ...
yenna_chata Posted September 8, 2014 Report Posted September 8, 2014 TSQL idea ledu, SQL ithe check the CPU cost, check the xplain plan....Run sql advisor through OEM.Major cost ekkada undo chusko and indexes emina avasaramo telusko
dotnetrockz Posted September 8, 2014 Report Posted September 8, 2014 ITS A CASE by case issue 1)first neeku access unte or dba daggarki velli profiler activate cheyyi and see whow much it is taking and which individual query is time consuming(assuming its a stored proc) 2)if ur joining to a interactive table(updates every few mins)...then there is a bottle neck...example is lets say fedex is shipping freight in a container and aa container ki every step ke oka db transcation record avuthundhi and lets say the conatine ris active since past 10 yrs...so like that if there are 10k containers....table size is large and if ur joining to such a table it will break ur quyery causing timeout 3()other than these check if ur waiting for any input or result from a stored proc call inside a transcation....this is very costly since ur making a call to a proc inbetween..if the proc returns the data its fine but if it returns a wrong format or irrrelevenat data...then there is a prob...just chekc how to handle retruning data. 4)for small opertaions dont use cursors...it may be time consuming instead just do with a SET/Update operations 5)make the order by to use date or integer columns ...this will be time effective 1
MegaPowerRockstar Posted September 8, 2014 Report Posted September 8, 2014 by default keep non clustur indexes on the columns that you use in where clause... unless other people or applications dont have objections.....
Uchiha Posted September 8, 2014 Report Posted September 8, 2014 ITS A CASE by case issue 1)first neeku access unte or dba daggarki velli profiler activate cheyyi and see whow much it is taking and which individual query is time consuming(assuming its a stored proc) 2)if ur joining to a interactive table(updates every few mins)...then there is a bottle neck...example is lets say fedex is shipping freight in a container and aa container ki every step ke oka db transcation record avuthundhi and lets say the conatine ris active since past 10 yrs...so like that if there are 10k containers....table size is large and if ur joining to such a table it will break ur quyery causing timeout 3()other than these check if ur waiting for any input or result from a stored proc call inside a transcation....this is very costly since ur making a call to a proc inbetween..if the proc returns the data its fine but if it returns a wrong format or irrrelevenat data...then there is a prob...just chekc how to handle retruning data. 4)for small opertaions dont use cursors...it may be time consuming instead just do with a SET/Update operations 5)make the order by to use date or integer columns ...this will be time effective Thanks bhayya..; inka ilanti steppulu unte konchem cheppava...
Uchiha Posted September 8, 2014 Report Posted September 8, 2014 konni reports slow running... So tables perform tune cheyali oracle DB... bebe aslem telidu epudu cheyaledu....inka emana steps unte cheppu bhayya paina detailed ga cheppav kada.. alaga.. Thanks
Pandu_age40 Posted September 8, 2014 Author Report Posted September 8, 2014 ITS A CASE by case issue 1)first neeku access unte or dba daggarki velli profiler activate cheyyi and see whow much it is taking and which individual query is time consuming(assuming its a stored proc) 2)if ur joining to a interactive table(updates every few mins)...then there is a bottle neck...example is lets say fedex is shipping freight in a container and aa container ki every step ke oka db transcation record avuthundhi and lets say the conatine ris active since past 10 yrs...so like that if there are 10k containers....table size is large and if ur joining to such a table it will break ur quyery causing timeout 3()other than these check if ur waiting for any input or result from a stored proc call inside a transcation....this is very costly since ur making a call to a proc inbetween..if the proc returns the data its fine but if it returns a wrong format or irrrelevenat data...then there is a prob...just chekc how to handle retruning data. 4)for small opertaions dont use cursors...it may be time consuming instead just do with a SET/Update operations 5)make the order by to use date or integer columns ...this will be time effective Thanks for your explanation bhayya
dotnetrockz Posted September 8, 2014 Report Posted September 8, 2014 Thanks bhayya..; inka ilanti steppulu unte konchem cheppava... i'll check my notes and reply but needhi oracle db antunnavu...nenu cheppedhi sql server related.....i know both are RDBMS....but execution plan theda undochu
JollyBoy Posted September 8, 2014 Report Posted September 8, 2014 Hello guys Tsql query okati long running unte how to reduce the time by increasing the performance ... I have seen many links but emana standard book or exclusively sql tuning medha with examples tho any links or books... Please help .. I appreciate your help ... query vey ikada
Pandu_age40 Posted September 8, 2014 Author Report Posted September 8, 2014 query vey ikada Query em ledu bro just personal interest .. Naku epudu chance rala real time lo cheitaniki .. Evarina real time lo Chesi unte how they handled telskundamani...best book to learn and know how it works telskundamani
Recommended Posts