Did you use this kit from evaluation.intersystems.com/Eval/community-download ?
=> IRISHealth_Community-2025.3.0.226.0-macos.tar.gz

Primary / Secondary  ?? Is this a shadowing configuration ?

Shadowing applies to the databases  IRIS.DAT, and Journal Files  
It doesn't shadow external "foreign" files like  .../Temp/QWhoZAwFF3f9jQ.iostream

Done!  😎

Did you also run a rebuild index ?
Just defining is not enough.

If you use a custom class query %Library.Query type you may write your parameters to some
^mtemp.Evgeny($i(^mtermp.Egeny)) = ..... direct from the Execute method
or ^mtemp.Evgeny($h) = ....

For basic class query %SQL.Query () you may take the usual SQL approach

• Create a SQL method that always returns 1 (TRUE)
• You pass all your parameters into that method 
  • which does the ^mtemp trick and a QUIT 1
• add to the WHERE clause  . . .  AND MYTRACE(par1,par2,---)=1

I refer to this a STATIC clause since it is only executed once by query
because of no reference to any column values 

It was my approach to SQL debugging
 

If your payload is received as a string 

set jsn={}.%FromJSON(payload)
write jsn.%Get("boolprop")

works without a persistent object

Probably because extending ObjectScript Functions in %LANGF00.mac is so simple for ages

ZLPAD(%txt,%len,%pad) quit $$lpad^%qarfunc(%txt,%len,%pad)
ZRPAD(%txt,%len,%pad) quit $$rpad^%qarfunc(%txt,%len,%pad)

and then

USER>s txt="robert"
USER>w $zrpad(txt,20,"*")
robert**************

USER>w $zlpad(txt,20,"*")
**************robert

$system.SQL.SetIdentityInsert(1) is deprecated and replaced by $system..SQL.Util.SetOption(IdentityInsert ,1) 

from class docs:>>>
https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic.cls?LIBRARY=%25SYS&CLASSNAME=%25SYSTEM.SQL.Util#METHOD_SetOption

Sounds good to me 

to be clear: 
USEEXTENTSET is great for very large tables where the top (with the ID) is many 
storage levels away from data blocks.
It's up to the dimension of your project if the eventual gain in speed pays off at all.
for small tables as we know from our samples, I doubt. 

As I expected, it's one of the new storage features that cause the irritation

/// Use hashed global names
Parameter USEEXTENTSET = 1

from docu  https://docs.intersystems.com/iris20253/csp/docbook/DocBook.UI.Page.cls?KEY=GOBJ_storageglobals#GOBJ_storageglobals_hashed

When you set USEEXTENTSET to 1, each index is also assigned to a separate global, instead of using a single index global with different first subscripts. Again, this is done for increased performance.

Not explicitly mentioned - this also affects  IDKEY !

And the example presented shows in detail that 
IdLocation and DataLocation are NOT identical anymore, as it used to be for decades
 

You can get the required Global reference like this programmatically:

 ; get compiled class  with your classname
USER>set classname="oex.Dir"
USER>set dic=##class(%Dictionary.CompiledClass).%OpenId(classname)
 ; get relationship to CompiledStorage
USER>set stor=dic.Storages.GetAt(1)
 ; get name of the ID-Global
USER>Write stor.IdLocation
^oex.DirD
USER>

I'm surprised that   data is already imported via SQL but ^myclassD has no content.
So take a look into the related generated class:

Storage Default
{
<Data name="DirDefaultData">
<Value name="1">
<Value>%%CLASSNAME</Value>
- - - - - -
after all properties
</Data>
<DataLocation>^oex.DirD</DataLocation>
<DefaultData>DirDefaultData</DefaultData>
<ExtentSize>986</ExtentSize>
<IdLocation>^oex.DirD</IdLocation>
<IndexLocation>^oex.DirI</IndexLocation>

 <IdLocation> is the one to go for
with all the new Storage strategies (columnar, sharded, ...  )
This might be quite an exotic global name and rarely the traditional.

I was right. 
My 7* review in OEX is still blocked by OEX censors, and your stars are suppressed.
24hrs are promised for reviews in OEX.

Just found it published now  [2026-01-04 13:18:45 UTC]

I run iris.script at docker start in this demo :  UDP
see docker-compose.yml.
It's for 2 containers. In your case half of it would be enough.