Hey Michael, how are you?

IIS weblog is very good idea, but the hitlog is not a large table, it is the log that has gotten large because I didn't understand how it would continue to grow without it being backed up.

I've created a maintenance plan for the future, but I would like to know how with code to manually shrink the log.

I've tried:

backup log mydatabase to mydatalog with TRUNCATE_ONLY

it doesn't like the mydatalog part.
I can't find any indepth articles, and all my books are terse on it.

TIA

>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.