This problem continues intermittenly.  The original if this error is System.OutOfMemoryException.  When this happens, it "locks" up the the entire DNN system (all portals).  Unfortunately, when this happens, the system gets really slow and bogged down until the out of memory exception pops up.  What's worst, all other portal users begins to see the System.OutOfMemoryException.

In examining the sourcecode, this exception is guarantee to happen on UDT with large amount of data.  The code is trying to load the entire data table into a dataset.  When it happens depends on the system load and memory size, so that's why it comes and goes.  It disappears when the aspnet_wp process recycles.

The solution that I'm currently using is to modify the UDT module with a new Render Type of "Express".  When this type is selected, no dataset is created.  Instead, I've added a stored procedure to only get the record count for display.  To navigate to edit a particular record, I'm using another SQL module that calls a store procedure which performs the pivot operation and add a "edit link" to each row; however, I greatly reduce the column count to keep the in memory table size small as possible.