Published on InterSystems Developer Community (https://community.intersystems.com)

Home > Which global mapping definition is better?

Question
Alexey Maslov · Jan 31, 2019

Which global mapping definition is better?

Sometimes global mapping of the same globals can be defined in different ways. E.g., I need to define it for 3 globals ^qAuditC, ^qAuditLog, ^qAuditLogC from the same database named APP-NOJOURN. Which approach should be better from the performance point of view?

1) qAudit* => APP-NOJOURN (one record in global mapping table)
or

2) qAuditC => APP-NOJOURN
qAuditLog => APP-NOJOURN
qAuditLogC => APP-NOJOURN (three records in global mapping table)

From one hand, the less records in global mapping table, the better. From other hand, * can cause additional processing at run time. Global mapping table for a namespace contains about 20 records and can be compressed to 15 ones if "unduplicated" such way.

Any advice will be great appreciated.

P.S. I'm pretty sure that there would be no globals masked as qAudit* but those listed above.

#Globals #Mapping #Namespace #System Administration #Caché #InterSystems IRIS

Source URL:https://community.intersystems.com/post/which-global-mapping-definition-better