Hi,

I would like to add three questions to this discussion.

First would any of you recommend the one instance with multiple parent portals for something like a bunch
of store front apps (CATALook for example or the DNN Store module)?

Second Larry mentions breaking out multiple portals to separate instances. How easy is that to do?
What if a customer that you maintain on an instance with multiple portals on a hosting site decides
to move his site to his own servers? In looking at the DNN database it seems that might be a little like
implementing a data warehouse ETL process. Would it be that easy to transfer all applicable database rows
and all the stuff in the DNN directory to the new fresh DNN instance? Will the DNN delete portal function
clean everything up OK in the old instance? I have tried out the portal export/import process. It seemed to work OK but
it was a simple portal with a few pages (Tabs) and no complex modules. Would export/import and the delete portal
function actually work OK in all cases?

Assuming there is a reasonable way to deal with breaking out multiple portals my intital thinking about this
subject was to setup separate instances for any DNN site that has a store front and to limit my other types
of instances to maybe 5 or 6 portals each. Does this plan sound about right or is it too conservative?

I am just starting to get into DNN. I go way back to when big iron was king. Anything with a label of
production on it makes me very paraniod. 

Thanks,
GM