Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LogsRemoveByDaysAndCount Error
#21
Yes and no - it is too much for a delete statement- because then every row is deleted, index statitics will be updated, transaction log is written - and if this is done some 100k it cost a really long time and it will lock the tables...

So if you need the logs you can- but then you can't cut these at program start :-) You deactivate it in Options=>Logs

If you use TRUNCATE TABLE Logs the whole table will be deleted in one transaction.that's really fast - as I used DELETE FROM Logs (will do the same) -it took about 10minutes...

Try "TRUNCATE TABLE Logs" and your problems should be gone - then decide how many logs do you really need- last 10 days, last 1000 entries??? Then it should be ok in the future...
Regards/Gruss
Oliver
Reply
#22
I've disabled the logs deletion on startup. Good to see that its stored in the database as well so new installations for my colleagues won't bug me with the same setting all the time.

Startup is now really fast indeed. I will discuss the logs deletion with our security guys.

Thanks for the help! Smile

Regards.
Reply




Users browsing this thread: 1 Guest(s)