This question is not about using a web farm. It is about running the DotNetNuke SQLDataProvider on a remote server. Read on...

I am in the process of developing a very large application using DotNetNuke 5.x with many custom modules which will provide the core of our business solution.  I've just been informed that due to a change in ownship of our company, our production environment must adapt to new corporate security standards which includes the policy that web servers shall reside in the DMZ and are not permitted to communicate directly with the database cluster behind the DMZ. The web servers are only permitted to communicate with application servers behind the DMZ which are permitted to communicate with the database cluster.

This is no problem for our core business modules as the UI modules communicate with the business logic and data layer using a web service. However, for DotNetNuke, I am puzzled as to how to get the SQLDataProvider to run on the remote app server. I was thinking I could possibly create a custom data provider which could use .NET remoting or WCF to communicate with a wrapper around the DotNetNuke SqlDataProvider running on the remote app server. Does anyone have any advice which point me in right direction to find an easier solution? Management just tossed a huge mud hole in front of my truck with this one.

Thanks All.