Instead of two separate fields, it would be easier to use the %TimeStamp (or %PosixTime) type, where the date and time are paired at once.
For this type of data, you can make your own indexes for different parts and/or combinations of them: a separate date, a separate time, a separate year, a separate year and month, etc.
You can also use these separate parts in the query (in SELECT and WHERE).

select datediff('yy',DOB,current_dateAge from yourtable

Made some minor changes to your code and now everything works as expected.

ClassMethod ActivateSQL(customerIdAs %Status
{
  ...
  Quit $$$OK
}

ClassMethod ActivateOO(customerIdAs %Status
{
  ...
  Quit $$$OK
}

If mode=0 {
  Do $system.OBJ.DisplayError(objCust.ActivateOO(id))
else {
  Do $system.OBJ.DisplayError(objCust.ActivateSQL(id))
  Set objCust.Active = objCust.ActiveGetStored(id)
}

Or

If mode=0 {
 Do $system.OBJ.DisplayError(objCust.ActivateOO(id))
else {
 Do $system.OBJ.DisplayError(objCust.ActivateSQL(id))
 Do objCust.%Reload()
}

Let's say you need to write a classmethod that updates a single property.

Update where: in memory or on disk?

Using SQL, you cannot update the value of a field in memory, but only on disk. On the other hand, OpenId() reads data from disk and knows nothing about the changes on disk that occurred after its call.

To avoid confusion, I would look to the side Version Checking (Alternative to Concurrency Argument) or/and <propertyname>GetStored()

I decided to try Columnar Storage (IRIS CE):

Property As %String(STORAGEDEFAULT "columnar");

When compiling a class, I get the following error:

ERROR #15804: Columnar Storage (STORAGEDEFAULT=COLUMNAR) is not available with this license

I turn to the documentation to find out what's the matter:

parameter INDEXNULLMARKER;

Override this parameter value to specify what value should be used as a null marker when a property of the type is used in a subscript of an index map. The default null marker used is -1E14, if none is specfied for the datatype. However %Library.PosixTime and %Library.BigInt datatypes could have values that collate before -1E14, and this means null values would not sort before all non-NULL values.

For beauty, I would also use the value of this parameter, for example:

Class dc.test Extends %Persistent
{

Property idp As dc.test;

Property idpC As %Integer(INDEXNULLMARKER "$c(0)") [ CalculatedPrivateRequiredSqlComputeCode = {{*}=$s({idp}="":$c(0),1:{idp})}, SqlComputed ];

Property Name As %String Required ];

Index iUnq On (idpC, Name) [ Unique ];

ClassMethod Test()
{
  ..%KillExtent()
  
  &sql(insert into dc.test(Name,idp)values('n1',1)SQLCODE,! ;0
  &sql(insert into dc.test(Name,idp)values('n2',1)SQLCODE,! ;0
  &sql(insert into dc.test(Name,idp)values('n2',1)SQLCODE,!! ;-119

  &sql(insert into dc.test(Name,idp)values('n1',null)SQLCODE,! ;0
  &sql(insert into dc.test(Name,idp)values('n2',null)SQLCODE,! ;0
  &sql(insert into dc.test(Name,idp)values('n2',null)SQLCODE,!! ;-119
  
  zw ^dc.testD,^dc.testI
}

}

Output:

USER>##class(dc.test).Test()
0
0
-119
 
0
0
-119
 
^dc.testD=4
^dc.testD(1)=$lb("",1,"n1")
^dc.testD(2)=$lb("",1,"n2")
^dc.testD(3)=$lb("","","n1")
^dc.testD(4)=$lb("","","n2")
^dc.testI("iUnq",1," N1",1)=""
^dc.testI("iUnq",1," N2",2)=""
^dc.testI("iUnq",$c(0)," N1",3)=""
^dc.testI("iUnq",$c(0)," N2",4)=""

Or

Property idpC As %Integer CalculatedPrivateRequiredSqlComputeCode = {{*}=$s({idp}="":$$$NULLSubscriptMarker,1:{idp})}, SqlComputed ];

Output:

USER>##class(dc.test).Test()
0
0
-119
 
0
0
-119
 
^dc.testD=4
^dc.testD(1)=$lb("",1,"n1")
^dc.testD(2)=$lb("",1,"n2")
^dc.testD(3)=$lb("","","n1")
^dc.testD(4)=$lb("","","n2")
^dc.testI("iUnq",-100000000000000," N1",3)=""
^dc.testI("iUnq",-100000000000000," N2",4)=""
^dc.testI("iUnq",1," N1",1)=""
^dc.testI("iUnq",1," N2",2)=""
Class dc.test Extends (%RegisteredObject%JSON.Adaptor)
{

Parameter %JSONENABLED = 1;

Property AppointmentID As %String(%JSONFIELDNAME "AppointmentID"%JSONINCLUDE "inout");
Property AppointmentType As %String(%JSONINCLUDE "inout");
Property AppointmentTypeID As %String(%JSONINCLUDE "inout");
Property Date As %String(%JSONINCLUDE "inout");
Property DepartmentID As %String(%JSONINCLUDE "inout");
Property Duration As %Integer(%JSONINCLUDE "inout");
Property PatientAppointmentTypeName As %String(%JSONINCLUDE "inout");
Property LocalProviderID As %String(%JSONINCLUDE "inout");
Property ProviderID As %String(%JSONINCLUDE "inout");
Property StartTime As %String(%JSONINCLUDE "inout");
Property Reason As %String(%JSONINCLUDE "inout");

XData AthenaAppointment
{
<Mapping xmlns="http://www.intersystems.com/jsonmapping">
  <Property Name="AppointmentID" FieldName="appointmentid" />
  <Property Name="AppointmentType" FieldName="appointmenttype" />
  <Property Name="AppointmentTypeID" FieldName="appointmenttypeid" />
  <Property Name="Date" FieldName="date" />
  <Property Name="DepartmentID" FieldName="departmentid" />
  <Property Name="Duration" FieldName="duration" />
  <Property Name="PatientAppointmentTypeName" FieldName="patientappointmenttypename" />
  <Property Name="LocalProviderID" FieldName="localproviderid" />
  <Property Name="ProviderID" FieldName="providerid" />
  <Property Name="StartTime" FieldName="starttime" />
  <Property Name="Reason" FieldName="reasonid" />
</Mapping>
}

/// d ##class(dc.test).Test()
ClassMethod Test()
{
  json="{""date"":""06/27/2022"",""appointmentid"":""1214525"",""departmentid"":""195"",""localproviderid"":""187"",""appointmenttype"":""NEW PATIENT 45"",""providerid"":""187"",""starttime"":""14:00"",""duration"":45,""appointmenttypeid"":""1188"",""reasonid"":""-1"",""patientappointmenttypename"":""New Patient""}"
  
  try{

    tmp=..%New()
    
    $$$ThrowOnError(tmp.%JSONImport(json,"AthenaAppointment"))

    $$$ThrowOnError($system.OBJ.Dump(tmp))
  
  }catch(ex){
    #dim ex As %Exception.AbstractException
    ex.DisplayString()
  }
}

}

Output:

USER>##class(dc.test).Test()
+----------------- general information ---------------
|      oref value: 3
|      class name: dc.test
| reference count: 1
+----------------- attribute values ------------------
|      AppointmentID = 1214525
|    AppointmentType = "NEW PATIENT 45"
|  AppointmentTypeID = 1188
|               Date = "06/27/2022"
|       DepartmentID = 195
|           Duration = 45
|    LocalProviderID = 187
|PatientAppointmentTypeName = "New Patient"
|         ProviderID = 187
|             Reason = -1
|          StartTime = "14:00"
+-----------------------------------------------------

PS: pay special attention to the reason field: is it a string or an array of strings?

The new version of IRIS 2022.2 has a new feature Columnar Storage, about which the documentation says the following:

Choosing a storage layout is not an exact science. You might need to experiment with multiple layouts and run multiple query tests to find the optimal one.

Therefore, you are unlikely to find an exact answer to your question.

Usually, the more efficient the query is and there are "correct" indexes, the smaller the GREF and, accordingly, the shorter the execution time. But this is influenced by many factors, not just the above: see InterSystems SQL Optimization Guide

This can be done much easier, for example:

Include %occUtility

Class dc.test Extends %Persistent ClassType = persistent, ProcedureBlockSqlTableName demo ]
{

Property Foo As %String SqlFieldName FooBar ];

Property Bar As %Boolean;

ClassMethod Test()
{
  
  ; d ##class(dc.test).Test()
  ..%KillExtent()
  
  &sql(insert into dc.demo(FooBar,Bar)values('f1',0))
  &sql(insert into dc.demo(FooBar,Bar)values('f2',1))
  &sql(insert into dc.demo(FooBar,Bar)values('f3',null))
  
  tablename=$$$comClassKeyGet(..%ClassName(1),$$$cCLASSsqlqualifiednameQ)
  
  rs=##class(%ResultSet).%New("%DynamicQuery:SQL")
  rs.Prepare("select * from "_tablename)
  rs.Execute()
  while rs.Next() {
    i=1:1:rs.GetColumnCount() rs.GetColumnHeader(i)," = ",$$quote(rs.GetData(i))," "
  }
  
  rs.%Close()
}

}

Output:

USER>##class(dc.test).Test()
 
ID = 1 Bar = 0 FooBar = "f1"
ID = 2 Bar = 1 FooBar = "f2"
ID = 3 Bar = "" FooBar = "f3"