Hey Folks

We have a new server intended for perhaps a dozen or so (client) webs

HP ProLiant  DL 360 G5
Xeon cpu / 4GB ram
2 raid sets R1(os) & R5(data-web)
Win Server 2008 web edition / IIS 7
SQL Server 2008 STANDARD

Second time around to implementing DNN as we have a lone wolf on an older production box .v4xx

Anyhow I want to get this right and optimal
We have a virgin server .. with intent for one web initially but plan for adding additional parent portals
What is the best setup for this scenario?

Do I create a WEBSITE for my initial DNN HOST (shell from which all production parent portals reside)
instead of a 'virtual' directory?

And likewise each additional parent portal ..should / can they be created as WEBSITE instead of 'virtual' directories?

With regard to SQL Server should I use data file (database.mdf) or database proper within SQL Server?

I probably could have gotten away with 'express' but the budget was available.

I have researched much of the documentation but there doesn't seem to be much with regard to this specific scenario OR maybe simply old braincells.

In IIS manager I have only 'Default Web Site' .. do I use it or create another entity for the DNN host, the host portal will simply use the server ip with host headers for client parent portals

Thanks for the opportunity. DotNetNuke rocks!..right?