I might be misunderstanding your question/suggestion.

Are you saying that DNN should create new databases for each portal that it creates?

Stuart

No, something completely different. Lets say you had a whole bunch of site built using SharePoint services. They are all independent from each other but use the same back end database, just like DNN. But what if each of these sites where for a project at your company. You could use SharePoint Server to aggregate the sites into a portal and do all sorts of cool things like search across all of them, set up personalized sites that pull data from selected children, etc.

But what if you could use DNN as the aggregator instead of SharePoint Server? It would require some way to search the SharePoint db and dynamically build content in the DNN portal. It's complex but probably quite doable.

I'm just wondering if someone had thought about it / done it / rejected it as impractical, that's all.