One way I could think of was to extend the object scope provider (gets
generated for you by OA Wizard when you enabled a project) to support
multiple Database objects (that is the Telerik defined Database class).
Because if you look at this
in the documentation it can take an XML configuration like the one below:
| <connection id="ArchiveConnection">
Now, the trick is to transform the information in your database to
something like the above, eventually including also the references
section at runtime
Like a method (still based on the original ObjectScopeProvider.cs)
called.... GetNewObjectScope(string datasourceId), where datasource Id
is the one you have in your table.
Within the GetNewObjectScope(string) method, you query your database
for the connection string, dynamically create a xml snippet and pass it
to the Database.Get(...) method as parameter.... Once you have the
Database instance you can store it within a Dictionary<string,
Database> type for further references.. and then you use the
instance to do a databaseInstance.GetObjectScope() like normally in the
Hope you get the idea. The link to the doc also has an example config, which should get you started.