I haven't been watching my site closely because it's just a demo site for the book, but I noticed today that there's a big build-up of records in the aspnet_profile and aspnet_users tables. This is caused by the way we're tracking anonymous users - we never clear out those entries and the tables keep getting bigger.

So, as a part of the routine maintenace of the site, these anonymous records should be purged periodically (maybe once a month). This SQL will do that:

delete from aspnet_profile
where userid in
 (select userid from aspnet_users where isanonymous = 1)
go
delete from aspnet_users where isanonymous = 1
go

And, of course, if you have set up any Custom Web Events, you'll need to purge that table also.

Eric

This is an update to the above SQL. Instead of deleting ALL anonymous users, it might be better to delete only the ones who haven't returned to your site in the last 60 days (or 30, or whatever number you like):

delete from aspnet_profile
where userid in
 (select userid from aspnet_users
  where isanonymous = 1
    and datediff(dd, LastActivityDate, getdate()) > 60)
go
delete from aspnet_users
where isanonymous = 1
  and datediff(dd, LastActivityDate, getdate()) > 60
go

And don't forget about the aspnet_WebEvent_Events table! I removed the healthMonitoring section from my web.config because I wasn't actually looking at the events, anyway. But this kind of monitoring can be good if you intend to keep up with it, and purge that table occasionally.

Eric

Thanks.

great.. thanks man

www.clubvwnica.com

is it ok to delete all data from aspnet_WebEvent_Events?

yes, you can delete the events. They're only there to tell you what happened. Think of it as an audit trail that can also help you debug problems.

thanks

Hi,

isn't the anonymous tracking used to check if for instance an anonymous user already voted ?

is there any manual on doing maintenance on the site ?

koen

The votes are stored in cookies with expiration settings here:
<ConfigurationProperty("ratingLockInterval", DefaultValue:="15")>