I am trying to combine two SolarWinds Orion (aka. A and B) DBs into one (aka. C), I didn't tried it yet but I hope it is possible.
I need to build some conversion tables, so A Polling Engine# 1, will not conflict with B poling engine# 1. Therefore, for example, I'll have to copy all references of A engineID# 1 to C EngineID# 1, and B EngineID# 1 to C EngineID# 2
It is the same for Nodes, and Agents. (not sure if there are more keys needed to be transformed)
The problem is that many foreighn keys are not appear in the DB, and are only implicit by names. For example: the table AgentManagement_Agents have PollingEngineID field which, I belive, referring to Engines table, but the reference between the tables has not been defined.
So I wonder, is there any document or diagram that can show all relation between tables, include the implicit ones?
Can I assume column names (like in the example above) are implies they are foreighn keys?
There is no public documentation of the table relationships, and you are correct there are many table columns that are not explicitly identified as being keys that you will have to comb through. Successfully combining two databases is extremely difficult and in most cases it doesn't go well. Hopefully you have plenty of time to get familiar with the table layouts and to experiment with how to move the data across.