I'm amazed that in the DNN SQL EventLog table that the LogProperties still uses ntext when it stores an XML value. 

I want to improve the event log reporting functionality but I really need to have the LogProperties stored as typed xml.

In my module I'm proposing the idea of adding a new column to the EventLog table.  I would create a persisted computed column which converts the ntext into typed xml using a schema I've created. 

I've now got this working ok in my test environment and can now query the logproperties on the event table very quickly using xquery.

However, I'm wondering are there any pitfalls to extending the EventLog table in this way?  Will updates to the DNN core remove the computed column?  Will the the core ever write text to the LogProperties column than doesn't follow the standard?

Thanks for any input to this.

Ross

Update: I know I could create a View which has the convert to XML in it, however, in my trial in a small DNN portal its 10 times slower (all cpu time) due to the on the fly convertion of the xml field on each row).