1. SMP > System Operation > Databases shows the size o your DB   8192 is the default you have to match te blocksize of your backup source
2. /usr/lib/iris/mgr/ is IRISSYS or the HS equivalent a direct restore may destroy your running installation. restore it in a parallel DB and import only uncritical parts.
3. in SMP > System Adnin > Config > Sys Config > Local DB  you can set the Blocksize of the DB before creation: Blocksize might be hardwired in Community Distribution 

Hi @Lorenzo Scalese 
I guess you are looking for class(%Utility).FormatString()

USER>set lb=$lb(1,"Lorenzo",2023,"RCC"_$c(13,10))
USER>write lb
      LorenzoçRCC
 
USER>zzdump lb
0000: 03 04 01 09 01 4C 6F 72 65 6E 7A 6F 04 04 E7 07         .....Lorenzo..ç.
0010: 07 01 52 43 43 0D 0A                                    ..RCC..
;;;;;  this is it
USER>set viewlb=##class(%Utility).FormatString(lb)
 
USER>write viewlb
$lb(1,"Lorenzo",2023,"RCC"_$c(13,10))
USER>zwrite viewlb
viewlb="$lb(1,""Lorenzo"",2023,""RCC""_$c(13,10))"

Your transformation produces  a YYYY-MM-DD HH:mm:SS string
in contradiction 
Property DOB As %Date;   expects an Integer similar to +$h 
The error is reported during Validation before %Save() of  your record

• either you change  Property DOB As %String;
• or use '$zdateh(source.DOB,7,,,,,,,,"")'   then ##class(%Date).IsValid(...)  is happy

add this line to your method OnPreHTTP()

 set %response.Headers("Content-Disposition")="attachment; filename=""your-file-name.some"""

With JOB you start an independent process in background.
You can pass any variable you may need.
But you can't pass the connection to the CSP page with all its settings.
the connection stays with the foreground job. 

According to class  Class Contatos.Amiguinho you presented
Class Contatos.Empresa should look similar to this to work:

Class Contatos.Empresa Extends %Persistent
{
Relationship Nomedaempresa As 
    Contatos.Amiguinho [ Cardinality = many, Inverse = Trabalho ];

Property Nome As %String;

Storage Default
}

Relationship is an Object concept that has no direct equivalent in SQL to handle it
The "MANY" end is basically just a piece of code ( RelationshipObject) to handle it.

By SQL you just can set it indirectly from the "ONE" end as you found yourself.
This is a real Property / Column that has a distinct value that you can touch and set
 

My 5th Choice:

• use  Native API for ObjectScript  for access.
• especially %Net.DB.Iris

BTW:
whatever your method does it always terminate with Quit $$$OK

so whatever happens it is equivalent to
set SphereJauh=1

I assume you look for a different return value ? Is it ?

your ClassMethod GetSphereJauh(Id..... is located in some Class

so just call it as any other class method

set SphereJauh=##class(classname).GetSphereJauh(ATTRDesc)  

the fact that this is used as part of a custom class query is totally irrelevant in this context.
it is straightforward ObjectScript. nothing else

Now it is obvious that ^realglobal has 11.3 times the size of ^testglobal
while your ^testglobal seems to have all blocks in buffers in memory
this is rather unlikely for ^realglobal.
So repeated reloading of blocks from disk seems to cause the delay
If you have the chance to double or triple your global buffers
you most likely may see improved processing of your $O()

check https://openexchange.intersystems.com/package/function-ISJSON-2 in OEX
and https://community.intersystems.com/post/function-check-if-string-json-object in DC

Hi @Vivian Lee !
I think you had no chance to see the problem in docs
You mentioned a custom class that extends %Text.English
this might be the cause of your problem.
The class is not visible in normal class reference (don't ask me why) 

Default %Text.English has a Parameter  NOISEWORDS100 =
"the of and a to in is you that it he for was on are as with his they at be this from I have or by one had not but what all were when we there can an your which their said if do will each about how up out them then she many some so these would other into has more her two like him see time could no make than first been its who now my made over did down only way find use may long little very after called just where most know get through back";

So you might be affected by these NOISEWORDS.
I failed to find any useful public documentation on this parameter and also %Text.Text is not too useful

Agree with @Julius Kavay 
Just read the documentation  on %CONTAINS
It's a function specific to data type %TEXT and is language dependant (more details in docs)
-------------------
If you look for a functionality as SQL LIKE you better use LIKE
or [ the contains operator of COS

%Get() in  %SQL.StatementResult.  does NOT act like $Get() in ObjectScript
You have to resolve the NULL value issue in your SQL statement using NVL() function with 2nd parameter.
More NULL Handling Functions

see official docs

• Release Notes
• Maintenance Release Changes for 2021.1.3
• Incompatibility History for 2021.1.3  

You still didn't understand the difference:

• - DATDEDIFF() works on local times  eg.  "1970-01-01" is your locale time  (eg. UTC+5.5 hrs)
• - $ZDT(...,-2)  uses by definition 1970-01-01 UTC

you should know from what time zone you  get your input from

#1 is correct

Your calculation #2 is seriously wrong.
reason
reading documentation you see
dformat -2 

And that's the mistake:
Your BirthDate is obviously considered as  LOCAL time
And therefore the difference you see reflects the time offset of your machine to UTC

-19800 sec => -5.5 hrs
system variable $ZTZ will show your offset to UTC in minutes  => -330
my guess: your machine is running at local time in India

 

for $ZTDH:
https://docs.intersystems.com/iris20231/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_fzdatetimeh
for $ZDT:
https://docs.intersystems.com/iris20231/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_fzdatetime

USER>r x
1997-08-09 10:38:39.700000000
USER>w $ZDTH(x,3,,9)
57199,38319.7
USER>w $zdt($ZDTH(x,3,,9),3,7)
1997-08-09T08:38:39Z
USER>w $zdt($ZDTH(x,3,,9),3,7,9)
1997-08-09T08:38:39.700000000Z
USER>