Pablo: "You should investigate the source of such log-in and log-out and maybe disable/deactivate it, like the creator of the discussion you mentioned did." Me: He solved the problem by shutting...
See more...
Pablo: "You should investigate the source of such log-in and log-out and maybe disable/deactivate it, like the creator of the discussion you mentioned did." Me: He solved the problem by shutting down his vMA (vmware virtual management appliance) which made all these Log-In and Log-Out entries. I don't have a vMA (even tho i had one a long time ago..). _But how you pointed out correctly i have to find the part of software that causes these logIn LogOut attempts. Pablo: "Then, talking about the transaction log, the transaction log records all transactions that occur on the database. Using simple recover, the database logs all transactions, but after the transaction is complete, it is deleted. It uses the least amount of disk space of all the models." Me: ...i have simple mode... Nevertheless the transaction log was 8GB even _AFTER_ successfully complete the transaction. In my understanding (and also your understanding) the T-Log should shink again after complete the transaction. (but it doesn't!!) What's next? - i try to find the cause of all these LogOn-entries. I'm interested in all information regarding the origination of these Log-entries. My best guess is Backup Exec 2012 (which definitely makes some of these events). I will come back with feedback...