It is possible that the search indexing process is causing some of the high db usage.  You could connect SQL Profiler to your db to try to identify problematic procedures and queries.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

I have been trying to upgrade to dnn 4.x.x

.net 2.0 installs but not correclty or something else is wrong.

I don't know if this will help figuring the problem out. This it the most recorded error in the event log.

(The Open Procedure for service "ASP.NET_2.0.50727" in DLL "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll" failed.  Performance data for this service will not be available. Status code  returned is data DWORD 0.)

when installed it pins the cpu to 100% for over 2 minutes.

all problems go away after i uninstall the .net 2.0 framework

none of my iis instances have to use the .net 2.0 for the cpu to go to 100% or the errors in the event log.

Any ideas other than install server 2003 and start again?