Mitchel:

I don't know if you saw a post a couple of days ago from somebody that was also having performance problems and they found that it was related to the log table.  I find all this very difficult to comprehend.  Honestly, 7,000 or 8,000 records in SQL Server should not make such a dent in the performance of any application, is like we are talking dBase III Plus here.  I don't know what it is, but something is very wrong for an increase of 1,000 records to significantly affect the performance.  Maybe it is the way the DAL is dealing with those inserts, but SQL Server should not break a sweat dealing with 8,000 records in a table, for any operation.

What do you think?

Carlos

Thanks for the replies,

It definitely brings up some points... even a hundred portals like I am hosting are really a drop in the bucket compared to what I'd expect the backend to be able to handle. Then there's always the comparison to the PHP ecommerce sites I have on the same server.. they always fly like new even while the DNN portals spin away in stasis.

I'd certainly expect a system like this to be able to maintain few thousand records without falling over... all very strange really.

For my Site log I've decided to reduce records to 7 days. That's plenty of time to allow owners to keep an eye on daily visits and referrers. Google analytics is definitely the product of choice for full stats and all portals have that installed. The tie-ins with Adwords and sitemaps are all highly worthwhile.

How about that users-online setting.... that has also been pointed at as a potential performance hit, but perhaps that's a left-over from early days?

Rob