will you please stop creating new threads with same content just because you didn't understand the replies you got (or you didn't explain what you wanted correctly)

this has already been...

neither of the options above will capture cases where the "joins" are old style.

and why not use the system dependency tables for it?

SELECT schema_name(o.schema_id) as  referencing_schema_name
...

this has already been discussed on https://www.sqlservercentral.com/forums/topic/case-statement-46 - if you need more/different info do follow it up there

question is incorrect and as such answer is also incorrect - both settings are used for SQL 2019 - one for first 32 cpu's, second for the ones above.

2 answers...

and look at not using cursors at all - in majority of cases where developers think they need cursors that is not the case

and what was the result when you tried it?

Wizard might be able to sort it out for you - but YOU need to put some effort on testing it yourself...

I think you misunderstood what I explained or you didn't implement it correctly.

doing it the way I mentioned the temp table created on proc B will have the contents inserted...

• This reply was modified 4 years, 11 months ago by frederico_fonseca.

not quite - it needs to be a temp table, not a table variable.

----THIS IS AN EXAMPLE OF PROC 2:
CREATE PROC dbo.Service_Data_Summary
AS

create table #MoreData 
(COLUMN1 INT
,COLUMN2 INT
...

• This reply was modified 4 years, 11 months ago by frederico_fonseca.

temp tables can be defined on proc A and referenced by any proc called by it

proc A calls proc B

proc B can then use the temp tables defined by A...

• This reply was modified 4 years, 11 months ago by frederico_fonseca.

you would keep the same functionality.

pseudo code - without seeing the proc this may be incorrect but should give you an idea

original code

OldProc

insert into original table from openquery...

select * from...

on the calling proc instead of doing an insert into define a temp table manually.

on the called proc detect and see if the temp table created on the outer proc...

its 10k partitions according to the OP

try "/ 12.0"

and 112 is wrong format for that date representation.

112 = YYYYMMDD

121 = YYYY-MM-DD HH:MI:SS.mmm

that is an Oracle feature - not available on SQL Server although parts of the equivalent features (SSAS) exist on SQL Server and can be controlled from T-SQL.