Viewing 15 posts - 1,441 through 1,455 (of 4,087 total)
It looks like you are using string manipulation to convert your CoverageEffectiveDateKey and CoverageEndDateKey from yyyymmdd format to mm/dd/yyyy format. DATEDIFF is perfectly capable of handling strings in yyyymmdd format, so don't...
December 15, 2017 at 11:34 am
December 15, 2017 at 9:41 am
Let me put this another way.
December 15, 2017 at 9:39 am
December 15, 2017 at 8:08 am
thanks for coming back to me. I can't really post expected results as I dont...
December 15, 2017 at 7:36 am
December 14, 2017 at 1:30 pm
You should also know that you can use CTEs to partially control the order of processing. The entire CTE has to be evaluated before it can be used later in...
December 14, 2017 at 9:25 am
December 14, 2017 at 8:08 am
Please post expected results.
Drew December 14, 2017 at 7:59 am
You haven't defined the relationship between the table that you are updating and the source data, so it's as if you're updating every single row in the table with every...
December 13, 2017 at 3:21 pm
And instead of using MONTH() try using DATEPART(QUARTER, <yourdatefield>)
Drew
December 13, 2017 at 3:13 pm
Here is an alternate method that does not require a pivot.
SELECT
*
FROM OPENXML(@hDoc, 'appt_links/appt_link',1)
WITH
(
[ResourceID] [nvarchar](10) 'Field[@name="ResourceID"]',
[FromActivityID] [nvarchar](10)...
December 13, 2017 at 12:02 pm
December 13, 2017 at 8:29 am
December 13, 2017 at 8:19 am
My solution is to use the right tool for the job. In this case it's a reporting tool such as SSRS.
Drew
December 12, 2017 at 1:29 pm
Viewing 15 posts - 1,441 through 1,455 (of 4,087 total)