SQL query taking a long time depending on the option -

-

i'm working on stored proc , thing 1 of options take 5 minutes run, of others takes 5 seconds.

declare @rpttype varchar(75) set @rpttype = 'audits'      select clt.[cltnum] [client number] ,clt.[clteng] [engagement] ,clt.[cltname] [client name] , clt.[csplname] [assurance partner], clt.[cmglname], e.[ddeventdesc] [project type], budget.[cbudprojectdesc] [project description], due.[cdtargetamount] [budget], min(wip.[wdate]) [1st date], cast(sum(wip.[wrate]*wip.[whours]) decimal(34,2)) [billable wip], cast( sum(ar.[arprogress])as decimal(34,2)) [progress], cast((sum(wip.[wrate]*wip.[whours]) - sum(ar.[arprogress]))as decimal(34,2)) [net wip],  cast(sum(bucket.[cinvar])as decimal(34,2)) [ar balence], max(inv.[invdate]) [last invoicedate], due.[cddatedelivered] [project otd date]from [sab].[dbo].[wip] wip     join [sab].[dbo].clients clt       on wip.[wcltid] = clt.[id]     join [sab].[dbo].[cltdue] due       on due.[cdid] = wip.[wdue]     join [sab].[dbo].[ddevents] e       on due.[cdeventid] = e.[id]     join [sab].[dbo].[invoice] inv       on wip.[winvnum] = inv.[invnumber]     join [sab].[dbo].[acctsrec] ar       on inv.[invnumber] = ar.[arapplyto]     join [sab].[dbo].[clientbuckets] bucket       on clt.id = bucket.id     join [sab].[dbo].[cltbudget] budget        on clt.id = cbudcltid         (@rpttype = 'audit - payroll' , e.[ddeventdesc] = 'audit - payroll' , ar.[artype] = 1 , (clt.[cmaster]=1 or clt.[cinvindiveng] = 0) ) or           (@rpttype = 'audits' , (e.[id] =   '132' or e.[id] = '133' or e.[id] = '134' or e.[id] = '135' or e.[id] = '139' or e.[id] = '140' or e.[id] = '142' or e.[id] = '178')                                                         , ar.[artype] = 1 , (clt.[cmaster]=1 or clt.[cinvindiveng] = 0)                                                        ) or           (@rpttype = 'reviews & comps' , e.[ddeventdesc] in  ('audit - review', 'audit -comp/disc','audit - comp w/o disc') , ar.[artype] = 1 , (clt.[cmaster]=1 or clt.[cinvindiveng] = 0)) or           (@rpttype = 'assur tax returns' , e.[ddeventdesc] in ('5500','720-pcori','8955-ssa','campaign report','corporate (1120-pol)','lm-1','lm-2','lm-3','lm-4','lm-10','lm-30','non-profit (990)','non-profit (990 ez)','non-profit (990-n)','non-profit (990-t)','schedule c letters','section 104d letter')  , ar.[artype] = 1 , (clt.[cmaster]=1 or clt.[cinvindiveng] = 0) )      group           clt.[cltnum],          clt.[clteng],          clt.[cltname],          clt.[csplname],          e.[ddeventdesc],          budget.[cbudprojectdesc],          due.[cdtargetamount],          due.[cddatedelivered],          due.[cddatereceived],           clt.[cmglname]     having sum(bucket.[cinvar])>0

'audits' 1 taking long.

presuming issue when @rptype "audits", thing notice different in case query on column "[id]" table [sab].[dbo].[ddevents].

there number of things cause run slower. first thing check whether or not index has been created on column [id]. if no index, why taking long.

another possibility is returning lot more data, taking longer normal.

as side note, instead of excessive use of "or" in part:

and (e.[id] =   '132' or e.[id] = '133' or e.[id] = '134' or e.[id] = '135' or e.[id] = '139' or e.[id] = '140' or e.[id] = '142' or e.[id] = '178')

you use "in":

and e.[id] in ('132', '133',' 134', '135', '139', '140', '142', '178')

the difference shouldn't affect performance--but make code cleaner.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more