Always good to hear differing methods. Optional parameters are the bane of my life, but that's a reasonable well established method of dealing with it, and fairly low cost...

Why questions are tricky!  

Ha, my recommendation is 2 procs so there's nothing to confuse.  If the OP wants to keep dealing with avoidable...

Yup, of course NULL does not equal NULL, but the fldinfo cannot be NULL (confirmed by OP).

So presumably @Parameter is optional and can be NULL. In which case the...

It's not the same query as the one the OP posted.  NULL does not equal NULL

Not quite the same as what the OP posted.  Here's another way but readability is not...

Imo it's easier to express as 2 queries

drop table if exists test_tblinfo;
go
create table test_tblinfo(fldinfo   int); 
go

insert test_tblinfo values (null), (1);

declare
  @parameter   ...

https://www.sqlservercentral.com/articles/the-numbers-or-tally-table-what-it-is-and-how-it-replaces-a-loop-1

https://www.sqlservercentral.com/blogs/tally-tables-in-t-sql

declare
  @start_yr         int=2020,
  @years            int=20;


;with
tally(n) as
(
...

The OP could generate as many years as needed with a tally table 🙂

declare
  @start_yr         int=2020,
  @years...

• This reply was modified 5 years, 11 months ago by Steve Collins. Reason: union all

Fwiw, adding meta data like ('ORD'+number and 'MO'+date) to database keys is not the best practice.  If you're stuck with it perhaps it's possible to add constraints which only allow...

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

Isn't this the same question from 3 weeks ago?

https://www.sqlservercentral.com/forums/topic/date-spans-for-continuoes-and-regular-dates-spans#post-3763906

There were some good answers offered

Another way

select s.salesman_id, s.salesman
from
  #salesman s
 cross apply 
 (SELECT COUNT(*) cnt FROM #customer  c WHERE c.salesman_id=s.salesman_id) xa
where
  xa.cnt>1;

drop table if exists #salesman;
go
create table #salesman(salesman_id int, salesman varchar(20));
go

insert #salesman(salesman_id, salesman) values 
(1, 'Tedd'),
(2, 'Fred'),
(3, 'Ed');

drop table if exists #customer;
go
create table #customer(customer_id int, salesman_id int, customer...

No...

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

Ok now it makes sense to me.   For some reason I thought the object_id() was going in the query and not the cursor.  In Azure SQL it's not allowed to...