Michael,

I've been thinking about your idea of using the IIS weblog, but if one wants to do lots of querying like hits per page, per hour, per day, per store, per x per transaction etc. wouldn't that be difficult since it is just a text log?

We are doing a lot with this table and it has been very useful. Over one year the hit log has only 3 million records of 10 fields. We can archive no problem.

Do you have any experience on IIS weblog versus a SQL Table?

>I'm with Eric. Can you aggregate the values on a daily or weekly basis?
>
>Also, why not use the IIS weblog instead of logging a record to a table?
>
>-Mike
>
>>A client let hard disk space go down to 3 megabytes on their database server when our largest table, a hitlog, was needing to allocate a new chunk to the table.
>>
>>Since the hitlog has an insert statement for every hit of the website, the whole site was down for 100 companies.
>>
>>After freeing up space and temporarily disabling the createhit method, the site resumed operation in a few minutes of the problem, but after about one half hour of operation the same 'storage unit is full' came up for some users.
>>
>>I'm fearing that that table cannot allocate more space that is available now, gigabytes worth, because it is damaged in some way.
>>
>>To solve the problem I had them delete 40,000 of our oldest hitlog records, but in a few days the table will have to allocate again and I'm not sure it will.
>>
>>Anyone have any experience with this area?
>>
>>The best idea I have is to create a new hitlog table.
>>
>>Thanks for any input.