sql - I have NULL results for thousands of rows. How do I exclude those from populating when they don't exist? -

-

i have code @ sales employee of mine. hired create growth on extinct customers. on 1,000+ customers have in dbase, effect 100. there have been lot of rows generated value null. want report exclude rows of customers more efficient in understanding management. how accomplish this?

    select  t1.cardcode 'bp code',         t1.cardname 'bp name',         count(case when t1.slpcode<>'37' t0.docnum end) '# of orders',         sum(case when t1.slpcode<>'37' t0.doctotal end) 'total orders amt',         sum(case when t1.slpcode<>'37' t0.doctotal end)/         count(case when t1.slpcode<>'37' t0.docnum end) 'avg order size',         count(case when t1.slpcode='37' t0.docnum end) '# of orders',         sum(case when t1.slpcode='37' t0.doctotal end) 'total orders amt',         sum(case when t1.slpcode='37' t0.doctotal end)/         count(case when t1.slpcode='37' t0.docnum end) 'avg order size'     ordr t0 inner join ocrd t1 on t0.cardcode=t1.cardcode    t0.docstatus = 'c'         , t0.canceled <> 'y'         , t0.docdate >= '2015-05-26'  group    t1.cardcode,             t1.cardname  order    t1.cardname 

select tnot.*, tyes.* ( select ocrd.cardcode 'bp code',               ocrd.cardname 'bp name',               count(ordr.docnum) '# of orders',               sum(ordr.doctotal) 'total orders amt'          ocrd          left join ordr             on ordr.cardcode= ocrd.cardcode            , ordr.canceled <> 'y'           , ordr.docdate >= '2015-05-26'           , ocrd.slpcode <> '37'       group ocrd.cardcode,               ocrd.cardname      ) tnot     join ( select ocrd.cardcode 'bp code',               ocrd.cardname 'bp name',               count(ordr.docnum) '# of orders',               sum(ordr.doctotal) 'total orders amt'          ocrd          join ordr             on ordr.cardcode= ocrd.cardcode            , ordr.canceled <> 'y'           , ordr.docdate >= '2015-05-26'           , ocrd.slpcode  = '37'       group ocrd.cardcode,               ocrd.cardname      ) tyes      on tnot.[bp code] = tyes.[bp code]    , tnot.[bp name] = tyes.[bp name]  order tyes.[bp name]

Comments

Post a Comment

Popular posts from this blog

Upgrade php version of xampp not success -

-
today decided upgrade xampp new php version (5.6.11). have downloaded , configured based on google said. after resetting server, runs successfully. when check xampp's phpinfo, has not been updated. screenshot what have missed? back htdocs files , database. download xampp . uninstall xampp control panel. manually remove xampp folder partition. install back problem solved
Read more

c - Bitwise operation with (signed) enum value -

-
i using enumerator values flags: typedef enum { = 0x00, b = 0x01u, // u has no influence, expected c = 0x02u, // u has no influence, expected ... } enum_name; volatile unsigned char* reg = someaddress; *reg |= b; according misra-c:2004 bitwise operations shall not done signed type. unfortunately, compiler iar use signed int (or short or char) underlying type of enums, , option can find relates size, not signedness ("--enum-is-int"). according iar c/c++ development guide arm , pages 169 , 211, can define type of enum s if enable iar language extensions ( -e command-line option, or project > options > c/c++ compiler > language > allow iar extensions in ide). in particular, should define "sentinel" value, make sure compiler chooses correct type. prefers signed types, , uses smallest possible integer type, sentinel should largest positive integer corresponding unsigned integer type can describe. example, typedef enum ...
Read more

xslt - Unnest parent nodes by child node -

-
in xml there items 0-n attributes , item should copied each attribute new item 1 attribute. given xml this: <?xml version="1.0" encoding="utf-8" ?> <items> <item> <name>a</name> <attributes> <attribute> <key>attribute1</key> <value>1</value> </attribute> </attributes> </item> <item> <name>b</name> </item> <item> <name>c</name> <attributes> <attribute> <key>attribute1</key> <value>5</value> </attribute> <attribute> <key>attribute2</key> <value>2</value> </attribute> <attribute> <key>attri...
Read more