I've seen many posts on DotNetNuke.com that DNN does not support MySQL or other databases - because scripts would need to be created for each module.  So... we're stuck with Sql Server Express (1 Gig of Memory and a .mdb size of 4 GB) or use the full-blown SQL Server.
My question is: 
If you're only using IIS, DNN  and Sql Server to host websites, what parts of SQL Server can be turned off?? 
Hopefully a lot... to speed up the delivery of the web pages.
Is there a .vb script / exe or something available that would make it easy to turn off all the un-needed parts/services?
Even a List would be nice.

BarryZ

So I understand that... SQL Server Express, with less overhead than SQL Server 2005, is as lean as it's going to get... to simply push out DNN websites.  OK.

Regarding the 1MB memory limitation and the 4GB max .mdb size:
I have three .mdb files hosting approx 30 websites.  The sizes of the .mdb's are:  128MB, 35MB, 65MB
The reason that they were split among multiple .mdb's was when newer versions of DNN were installed, they were first installed into a separate .mdb, then the other .mdb's were updated.
How does the 1MB memory limitation apply to multiple .mdb's?
Would it be better to have all 30 websites in one large .mdb?
... or would it be better & easier down the road if each website had it's own .mdb for backups purposes?
... There are times when an Administrator messes-up their website and only their website needs to be restored to the previous backup.  I'd rather not affect all other websites.

Can multiple instances of Sql Server Express be run?  Each with their 1MB memory limitation?
The W2K3 computer has 4GB of memory.

I also understand that you can tell IIS that each .mdb or even each Website can be in a separate IIS Application Pool, but I haven't gotten that deep yet.

Thanks for the advice.
BarryZ