Viewing 15 posts - 1,831 through 1,845 (of 4,087 total)
The OP should be able to solve this by adding SQL Server Central as a trusted contact.
Drew
March 1, 2017 at 10:52 am
It's a bad idea to use a NULL value to represent an unknown future date, because it forces you to use either a function (ISNULL or COALESCE) or an OR...
March 1, 2017 at 10:30 am
SELECT *
FROM
(
Values (135,'Acute lymphocytic leukemia','Females' ,0.23)
, (136,'Acute lymphocytic leukemia','Males' ,0.11)
, (138,'Acute myeloid leukemia','Females',0.34)
, (139,'Acute myeloid leukemia','Males',0.13)
, (141,'Anus','Females',0.44)
, (142,'Anus','Males',0.55)
, (144,'Bladder (including in situ)','Females',0.76)
, (145,'Bladder...
February 28, 2017 at 3:18 pm
I would use a CTE that included ALL of the aggregates and then in your main query use a CASE expression to choose which of those aggregates to actually include.
February 28, 2017 at 3:03 pm
February 28, 2017 at 2:53 pm
February 28, 2017 at 2:43 pm
February 28, 2017 at 9:15 am
I did something like this until one of my coworkers mentioned that she was red/green colorblind. I changed it to three "lights" with the appropriate one "lit".
Drew
February 27, 2017 at 2:38 pm
/**** CROSS APPLY: This will perform well if LIC is dense (many licenses for each facility)
and there is an appropriate index on at least FacilityID and License_Expiration_Date. ****/
February 27, 2017 at 2:25 pm
February 24, 2017 at 12:27 pm
Viewing 15 posts - 1,831 through 1,845 (of 4,087 total)