Cathal,  thanks I am looking at your sample app now.  Basically we want to replace the DNN 4.3.2 Profile provider with a true SQL table with extra fields like SQL Image.  If the table is replaced what fields is the DNN 4 core expecting to find in the Profile?  There must be some defaults fields that need to be stored in a new Profile to still work with the core.  Example UserID must need to be in there right?

We want the Profile table to still work with all the core features, just be in a true SQL fixed table/field format (that we can add our own custom fields to to be access by 4.3 modules we have created... such as user Photo as a SQL Image type).

I agree with Sebastian that the new profile capabilities should cover your needs (though it's Charles Nurse not Dave nurse you should read - it's at http://www.dotnetnuke.com/Community/Blogs/tabid/825/BlogID/15/Default.aspx ). If you don't have the ability to upgrade or use the latest version for some reason take a look at the table profile sample @ http://www.asp.net/downloads/teamprojects/default.aspx?tabid=62

Cathal

Cathal,

Thanks for the reply. I have been looking at the SQLTableProvider which seems to be just what we need in DNN 4.3.3 but I am unsure as how to replace/extend the DNN Profile provider to use it.

The problem is we cannot easily use the Serialized BLOBs to manage over 100,000 users with extended data elements and be able to run reports on this non-standard storage format.  We need to be able to use Microsoft SQL Reporting Services to quickly run reports on our DNN User Profiles and to be able to manage this table with standard normal SQL queries to named fields in a table.

Is it possible to extend/overload or replace just the DNN 4.3.3 SBLOB Profile table to support plain normal SQL fields?

We don't want to customized or break anything in the core - just be able to store the data in a normal SQL schema. I understand that this will force all portals to have the same fields for profile storage, and this is not a problem since we (and most sites) are only running a single default portal.