I am building a simple Transactional App and considering doing it as a module.

I like the idea of some layout flexibility and the ability of my client to and and maintain additional modules - just text/html modules - but am struggling with two issues and would appreciate any comments ...

1. Can I justify the incremental cost of adding SQL Server to the stack (The app uses MySql, so MSSQL would be part of the cost of using DNN)?

2. What overhead will the DNN framework add?

The first of these is clearly just cost/benifit based decision specif to my situation - the second invites discusion as to

A. Once you're supporting .Net2.0 on IIS, how much more load is DNN?
B. Are there core mods that can be made to DNN to shrink resource requirement footprint (presumably, at the cost of some functionality).

Thanks