the date format is most suspicious to me.
in SMP you can set it to
- Logical Mode  >>>  66453  like +$horolog
- Display Mode  >>> 2024/03/25    as you did. It is depending on default display settings.
- ODBC Mode    >>>  2024-03-25

more drastic: KILL  does an ObjectScript Kill on all related Globals. Quick and Fast
DELETE loops on subscripts and mimics a SQL DELETE row by row and has definitely more overhead
 

LOAD DATA requires activation of JavaGateway.

>> active in docker community version by default

your CASE statement  is wrong in multiple ways:
and doesn't work in ENSEMBLE /Caché either

1. double quotes " mark column names, strings require single quotes '
2. !=""  is an Objectscript construct
3. you have to write NOT IS NULL instead 

select CASE WHEN StarterKitName NOT IS NULL THEN ....

See also example in ENS/Caché  docu :
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_case 

As you now explained what you really are looking for:   $System.SQL.Schema.SetDefault()

From Docu:

classmethod SetDefault(schema As %Library.String = "", ByRef oldval As %Library.String, Namespace As %Library.Boolean = 0) as %Library.Status

Sets the default schema used by SQL.
This configuration setting provides the ability to define a default schema name other than SQLUser, the default. When an unqualified table name is encountered in an SQL statement (and there is no #import statement specified), the default schema will be used. This setting has nothing to do with the mappings between SQL schema names and the class package name, it only specifies the default schema. Parameter:

schema

String containing the default SQL schema name. If schema is "" or not defined, the default schema will be set to SQLUser.

oldval

Passed By Reference. Contains the previous value of the setting.

Namespace

Boolean 1/0 flag. If TRUE, set the default schema for the current namespace only. The default for Namespace is FALSE

Returns:

Status Code

NOTES:

- You must have the "USE" permission on the %Admin Manage Resource in order to change this configuration setting.

- Changing this configuration setting will affect all processes immediately.

Hi @Michael Davidovich !
you hit exactly what I addressed in in my recent article
  The bewitched line terminator

As long as you get (text-) files from your own OS the default is OK
BUT: if you work cross OS platforms - rather likely for CSP pages -
the approach of  %CSP.BinaryStream is the best for import.

For output stream you have to decide based on the expected target OS.

My personal trigger to that subject was file transfer between
WIN as Docker host and a Container (Ubuntu) causing a lot of  confusion until detected.
 

System Utility %ETN.int takes a snapshot with all actual variables somehow similar to WRITE command
Description:  Using %ETN
It may give you some feeling how to analyze a running process.
ATTENTION: 
reading requires some experience in ObjectScript
you might get lost

you describe 2 different record layouts that reside within the same storage 
#1 - just a name
#2 - a name + a "transferred" property

depending on the situation you use either layout #1  or layout #2 for INSERT
reading might be OK for layout #2 in both cases.

Caché once had a somewhat similar sample with Person
and Employee extending Person. 
available here: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=ASAMPLES
this Repo:
https://github.com/intersystems/Samples-Data/tree/master/cls/Sample

eventually better to check for longer lists

USER>s x=$lfs("Purple,Black,Yellow,Pink")
USER>s y=$lfs("Red,Green,Orange,Yellow")
USER>f z="y","x" f i=1:1:$ll(@z) i $i(dif($li(@z,i)))
 
USER>zw dif
dif("Black")=1
dif("Green")=1
dif("Orange")=1
dif("Pink")=1
dif("Purple")=1
dif("Red")=1
dif("Yellow")=2
 

looping with $o() over dif() allows programmatic check

nothing official

Once upon a time ...

• there was an operating system named VMS
• running on computers named VAX and ALPHA
• The syntax to access a file was  drive:[directory] 
• it's the same structure used by RSX-11/M, RSX-11/D, RSX-11/S on PDP-11 processors

So on drive DUA1  you refer to director TEST3 

default super Server port = 1972   !

set int = +testingID

same using USE 0:(:"/ECHO=0"")   and  USE 0:(:"/ECHO=1"") 
or
Use 0:(":"S") and Use 0:(:"N")   for "silent" and "normal"
more docs

my private hack for this situation:

ClassMethod MyMethodPost() As %Status
{
    $$$LOGINFO("JobId: "_$JOB)
    kill ^%kurro
    set ^%kurro(0)=$JOB
    for  {hang 20 break    quit:$get(^%kurro) }
#; just hang around until ^%kurro =1
    ..... 
    Quit $$$OK
}

You can map PACKAGE [aka. SQL Schema] to another Namespasce (not a single table)
e.g. Bna.Utils to namespace %ALL or just to a specific namespace
so you have Table and Class  (= the code) available.

If you want to share also DATA  you need to map also  the related Global 

ChatGPT is just stupid and has no idea of IRIS / Caché
A TABLE will by default never have the same name as the GLOBAL that stores the content
>>>> HS.IHEX.RecordHistory and the global ^HS.IHEX.RecordHistory  <<<<<
HS.IHEX.RecordHistory is definitely not a handcrafted table.

Hi @Daniel Aguilar 
for every DB you have a default collation that is tied to DB:
you can see it in SMP  System > Configuration > Local Databases > Database Properties

this is the standard.
If the collation of your source server is Spanish, German, Fench, , .... 
the DB may have used this national collation as default.

On your target serve you need to have this collation to be installed.
in SMP  System > Configuration > Locale Definitions you see what is installed on your Caché instance

You may need to add the missing collation table to your Caché instance: