• Thanks for your reply

    The Recovery Model is simple.

    There is no defined (or we can't catch it) reason why it should go like this. It is part of a cluster with one server active all the time and the second is used for fail over, and has two SAN drives.

    One drive has the database on, currently standing at 384gb with an allocated space of 750gb. The sedond is the QUORUM.

    When it happens it just goes wild. When I restart the SQL service it settles down, but with a second of two off it goes again.

    When I issue the ALTER DATABASE command it does not necessarily work straight away, I may have to issue it several times before it takes.

    Once it is reset, it stays stable for a while, but once again, there does not appear to be any one thing that starts it off.

    I hope this makes sense...