I think I've seen somewhere that DNN 4.7 supports the use of two separate sets of connection information; one that is used for normal day to day access and one that is used to install modules (which needs higher rights in the database).

We are trying to harden DNN as far as possible and one of things I've done is create a database user with rights to execute all the SPs/UDFs etc. and select on all the views, which I will be using for every day operation. However obviously this user account has insufficient rights to create new database objects, a requirement for installation of additional modules. I would like, in our development environment only, to test out the concept of elevated privileges for installation of new modules. Can anyone help me on how to configure the second set of connection information? I thought it was something like an attribute in the string called installConnectionString but a Google has revealed nothing.

Please note that I am NOT referring to the old and new style connection strings maintained in the .config file. I fully understand that the ASP.NET 2.0 connection string is now used for most core stuff and the other kept for backwards compatibility with modules. I am an experienced developer and my question is not an everyday one. Instead it revolves around the system's ability to SWITCH ACCOUNTS so that installation of modules takes place under a database account with elevated privileges. This is something most users (95%+) will not bother to do, but which would (given sufficient experience and access to separate environments) provide significant hardening of database security.