I’m having a bit of trouble figuring out this issue. After our midnight database index rebuild this past Saturday our TRN files have been getting abnormally large. They’re usually about 40-60MBs and now every night after our 8pm full SQL backups run at about 3-4am the TRN files start growing to up to 20-30GBs. They’re set to run every 10 minutes so the backup repository quickly runs out of space. I’m not seeing anything out of the ordinary in the logs. Has anyone had this issue before or any ideas what I can look at?
I would suspect that you have a process that the System Agent runs at some point that is having an issue. Probably a large query for a report or something like that. It may look like it finishes, but the way it is designed, it’s using an awfully large amount of transactions and/or temp space - perhaps a runaway process like MRP that is having an issue and SQL finally terminates it before everything crashes.
Agree with Mike… look for any Epicor scheduled tasks running at that time. I could totally see this being MRP maybe with too many Change Logs hitting the Job tables. There was a good thread from @timshuwy on that a while back. I have seen it first hand where bad Change Logs blow up the T-log out of control…
But as Greg said, if you’ve totally ruled out Epicor then perhaps something else is going on with the SQL Server. The sp_whoisactive command is my go-to to see what’s going on. Activity Monitor is good too. Profiler gets you more but more work to use.