Think I've sussed it, basically add an extra field assigning a number value for each range I want and use that for the pie data.

Ignore, I've sorted....:crazy:

Ok, so it turns out there were half a dozen jobs created to purge status/events that were just taking forever to...

GilaMonster (11/11/2010)

---

That means you have a long-running transaction open that's keeping the log large. You need to identify and fix that and whatever caused it before you decide what to...

The log seems to have peaked at 50GB and looking at the % used it's slipped down to using about 35GB so I will keep an eye on it. Thanks...

Ah ok, I misunderstood then. I will give the log some more room to grow, but considering the db is only 40GB, this seems large. I could split the log...

Thank you, but I have read the article and have done what both it and you suggest but it does not work.

I returned to full, ran a full backup, ran...

I've set it back to full, running a full backup again. Then will try "BACKUP LOG dbname" is that the correct format? WITH TRUNCATE_ONLY no longer works as it's deprecated.

Hi, I did read the article yes but unfortunately it doesn't help. When I was in "full" I got the error "full backup does not exist" when I tried to...

I am in Full, it may be better setting it to simple then, see what happens!

OK, I managed to merge the 2 database files by doing the following:

1) Setting the database to single user mode

2) Detach the database file

3) Move files to the same folder...

Thanks guys, that was the fix, could have sworn I posted a reply, sorry for that!