John,

The business needs of the individual portals/clients should decide the creation of either a full site or portal. In my humble opinion, creating a single DotNetNuke site with several portals for different clients is not ideal. However, with that said, your client's needs should dictate.

If your clients have no special needs and leave everything up to you than that's perfect. Some clients do not have the same upgrade paths due to 3rd party modules being used, or preferring a specific version of a core module (e.g. the blog module).

I also like to separate client sites into different Application Pools so each is isolated, this way if one client is experiencing a problem - the rest don't suffer from the same issue.

On the other hand....you can certainly run a site with several hundred or thousand portals if you wish, i would think that it just becomes a maintenance nightmare and a real hog of system resources!

Take care,

Ian

Thanks for those responses.

Out of interest faolling that route. How much resource do you give over to each client instance and out of interest what size is each db normally sat at?