In theory it should be possible but maybe not easily.  The tvf is parameterized so I think to remove it would require splitting...

The query could be without the cte

select
  t1.id, cast(t1.startdate as date) startdate, cast(t1.enddate as date) enddate, cast(td.enddate as date) range_end_dt
from
  dbo.test_1 t1
 cross apply
 ...

The OP wrote: "output is expected as if member is continuously enrolled without any gap in enrollment get min and max and if there is enrollment gap leave as is." ...

To resolve for arbitrary relationships in the data requires hierarchical recursion, no?  The OP's question and Phil's too

drop table if exists dbo.test_1;
go
create table dbo.test_1(id int,startdate datetime ,enddate...

drop table if exists dbo.test_T1;
go
create table dbo.test_T1(
  ID1       varchar(8) not null,
  ID2       varchar(8)...

• This reply was modified 5 years, 3 months ago by Steve Collins.

In 2016 there are some nice built in features to support time zone conversions

/* the list of time zones your instance supports */
select * from sys.time_zone_info;

declare
 ...

this

declare @frDate         date='2020-03-31';

with a_cte(DocType, Debit, Credit, Account, Mdate) as 
    (select 'TC', 10, 20, 123, '2020-03-30'
...

That's what the OP wrote but is it what they meant?  🙂  Idk

Try adding this to your WHERE clause:

      AND NOT (
           ...

• This reply was modified 5 years, 3 months ago by Steve Collins.

As separate statements maybe something like this

set xact_abort on;

begin transaction;
begin try
    update g
    set
      [skuId] =...

• This reply was modified 5 years, 3 months ago by Steve Collins.

JsonAutoService

And what does this sentence mean... "It isn't (and wasn't) possible to access the request route values from within the program delegate." ?...

Ok Jeff, I'll do whatever you suggest.  I'll submit something.

I'm intrigued, but I have absolutely no idea what this looks like in practice. Have you got a friendly introduction somewhere? Video? Some code to look at? And what...

It's an interesting approach.  I've cloned the repo.  Two things I like based on initial impression are the intellisense on db objects and the C# unit test codegen.

It's great to see this article!  I'm going to sit this pie fight out though.  Two items I would toss in fwiw:

1. The return type of the SCOPE_IDENTITY function is...