I've recently expanded the use of AF Analytics on my system and I'm getting "The transaction log for database 'xxxx' is full" messages being logged and the AF Analytics service seems to hang up.
We're currently investigating the size, etc. of the transaction log for the database, but I'm interested in what causes transactions to be logged in this way on a normally running system which is not being changed as this may affect the way we implement the analytics going forward.
Any tips for optimising Analyses to minimise the impact on the SQL database (eg updates, transactions, etc). Would be very useful.