I've got the room for everything it is the transaction log that has been growing, and I had an hourly backup of database but didn't know how to backup transaction log.

I tried:
backup log mda to mdalog with TRUNCATION_ONLY
but it doesn't like the mdalog part.

Any ideas? I find very little in books on this.

>Is there some why you could aggragate the data on a time interval, ex every night or week, therfore removing old records but keeping all the statistical information?
>
>Eric
>
>
>
>>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.