Should I store OPCUA object addresses in a database ? Seeking experience & good practice|OPC UA Standard|Forum|OPC Foundation

Hello,

I've recently join an MES project that implies connecting existing machine with the OPCUA protocol.
The idea would be to connect a plant, make it standard, and replicate it to another plant. OPCUA was chosen in this project in order to have a healthy standard from which we can build upon and I have documented myself a little bit about it.

I will attempt to describe a situation from which I can't understand it's outcome but maybe my understanding of OPCUA corrupt the immagined situation:
Let's say I have set up an OPCUA Information Model, connected my machines and for example, set up a Node-Red application to read some machine variables. Everything was mildly-easy because I am on site, I know my machines well, I know what to get from them, and as I set up Node-Red, I know my machines and their variables OPCUA url.

If I want to copy this to another plant, and then manage it from afar, wouldn't it be recommended to store every address in a database? For example a relational database:
MachineTable: MachineID, MachineName, MachineOPCUAaddress  |  VariableTable: VarID, MachineID, VarName, VarOPCUAaddress

By doing so, everybody will be able to see how to get to any machine and the data it produces. But also be able to update if necessary, maintain, etc. Is it a good practice, am I missing the whole point of OPCUA?

Please share your knowledge with me, I haven't been able to find an answer to this in the OPCFoundation documents and I am also new to the industry. Thank you.