Just going from what is said above:
If you have sufficient bandwidth and sufficiently low latency to make a db connection reliable, then you have sufficient connectivity for pollers on the other Site.
Why not use that?
If you need to easily divide up views, reports, permissions it would be easily accomplished just using a custom property for "Site" Fill in a location, say
IslarNubla and IslarSorna, for Site A and Site B. From there, use that in your reports, view restrictions, account restrictions and such to divide up who can see what
BUT - you would still be able to gather reports from all devices.
Perhaps someone will post differently, but I do not believe you will get any official blessing from SolarWinds support to run two different installations to one single database.
Upgrades would certainly be more problematic, and custom properties updating the schema would likely cause some havoc as well.
Thanks for replying, just to clarify (& I prob didn't explain the situ precisely initially) bandwidth, latency wasn't the issue. The issue boiled down to the fact that the separate network had a, how can I put this, complex IP schema & there were routing issues surrounding this aspect...
That said, I've had some additional information this morning concerning this particular setup & it appears that this is no longer an issue anyway! Which is good news for me
Interesting to know that potentially this is possible, but given the (most probably) high overhead in terms of configuration etc, not really viable.
If anyone else has points to make ref this, I'd certainly be interested to hear them.
Thanks again dstoney