# E10 Production Trans Log File Growth **URL:** \ **Category:** Epicor ERP 10\ **Tags:** sql\ **Created:** [May 9, 2019, 2:56pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531 "2019-05-09T14:56:18Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 9, 2019, 2:56pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/1 "2019-05-09T14:56:18Z")
We went live with Epicor 10 this week. Our Production trans log file is growing at an enormous rate. We are currently syncing our production db to AWS which means our recovery mode is set to full. If we set to simple, we break our sync. How can we automate the log shrink leaving recovery mode set to full? Support actually told us to set our max log file size to 10GB and our initial size to 256MB which will “prevent growth.” And of course Epicor crashed this morning because our trans log hit its limit. Any help would be greatly appreciated. ---
**Author:** ![danbedwards](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9f8e36/32.png) [@danbedwards](https://www.epiusers.help/u/danbedwards)\ **Post date:** [May 9, 2019, 3:07pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/2 "2019-05-09T15:07:41Z")
If you can prevent it you do NOT want your log auto-growing - only in emergency situations. I would set the Initial Size to something that is more rational. I would look at making it 25% of the size of your database and if you are seeing average log growth per day of x MB I would set it according to what that look like. For example, if you log is growing 2500MB every day then I would allow for at least twice that in initial size so you get rid of auto-grow event. The next item would be to properly checkpoint the log and then add proper log backups / truncate which will keep the log file in check. I guess one question would be when you say “syncing” what are you using for this? There might also be an underlying reason that causing the log to grow that can be eliminated. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 9, 2019, 3:10pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/3 "2019-05-09T15:10:14Z")
We use AWS for Disaster/Recovery. ---
**Author:** ![danbedwards](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9f8e36/32.png) [@danbedwards](https://www.epiusers.help/u/danbedwards)\ **Post date:** [May 9, 2019, 3:11pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/4 "2019-05-09T15:11:20Z")
Right - are you just taking a full backup and sending or something more real-time? Syncing sounds replication like. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 9, 2019, 3:12pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/5 "2019-05-09T15:12:05Z")
Yes, its on the fly sync to AWS in case we have a DR scenario. Its a simple process to flip the switch over to AWS so the business can keep running. ---
**Author:** ![Alexandre\_Pothier](https://www.epiusers.help/user_avatar/www.epiusers.help/alexandre_pothier/32/5421_2.png) [@Alexandre\_Pothier](https://www.epiusers.help/u/Alexandre_Pothier)\ **Post date:** [May 9, 2019, 3:16pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/6 "2019-05-09T15:16:40Z")
10 Gb is far from being enormous. Unless you perform less transactions in the system, you can’t prevent transaction logs from growing and you shouldn’t restrict it’s size. The most important thing is to make sure you backup transaction logs multiple times a day, which will prevent from growing out of control. At some point, it will reach his “maximal” size based on what is going on in your system. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 9, 2019, 3:17pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/7 "2019-05-09T15:17:13Z")
Are there any obvious signs i can look at in the db properties to find out why it would be growing so fast? It seems like it grows almost 10GB daily. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 9, 2019, 3:18pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/8 "2019-05-09T15:18:50Z")
OK. So it should be as simple as setting up a trans log backup to happen every hour and that will prevent the log file from growing the way it has been? ---
**Author:** ![danbedwards](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9f8e36/32.png) [@danbedwards](https://www.epiusers.help/u/danbedwards)\ **Post date:** [May 9, 2019, 3:20pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/9 "2019-05-09T15:20:06Z")
Yes > [@danbedwards](#): > > The next item would be to properly checkpoint the log and then add proper log backups / truncate which will keep the log file in check ---
**Author:** ![Alexandre\_Pothier](https://www.epiusers.help/user_avatar/www.epiusers.help/alexandre_pothier/32/5421_2.png) [@Alexandre\_Pothier](https://www.epiusers.help/u/Alexandre_Pothier)\ **Post date:** [May 9, 2019, 3:21pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/10 "2019-05-09T15:21:56Z")
Any transactions going on in the system is kind of backed up in transaction logs. Processes like MRP can generate a lot of data movement and then increase the size of the transaction logs. Again, 10 GB is not that huge. I can’t evaluate what you can expect since I don’t know what is going on in your system, but you should plan to reserve something like 50 GB for transaction logs. And YES, it is critical to take transaction log backups. ---
**Author:** ![danbedwards](https://www.epiusers.help/letter_avatar_proxy/v4/letter/d/9f8e36/32.png) [@danbedwards](https://www.epiusers.help/u/danbedwards)\ **Post date:** [May 9, 2019, 3:24pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/11 "2019-05-09T15:24:58Z")
One thing that may cause a roadblock with the theory of the log backups keeping your log clean is long running process / active transactions. If you have this scenario going on no log backup will help you because of uncommitted transactions. I would track down the source of your log growth and make sure you understand why it is occurring. There are quite a few tips on the web for tracking down long running processes, etc. in SQL. ---
**Author:** ![MiguelS](https://www.epiusers.help/user_avatar/www.epiusers.help/miguels/32/99_2.png) [@MiguelS](https://www.epiusers.help/u/MiguelS)\ **Post date:** [May 9, 2019, 3:33pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/12 "2019-05-09T15:33:32Z")
Make sure you dont have trace logs set on your users accidentally. Sounds similar to our issue when we went live. Ours was resolved through backups. ![image](https://epiusers.help/uploads/default/original/3X/3/9/39f8a59f294d69d0bb9a2a3544312350c7cbd57f.png) ---
**Author:** ![enbw](https://www.epiusers.help/letter_avatar_proxy/v4/letter/e/ce73a5/32.png) [@enbw](https://www.epiusers.help/u/enbw)\ **Post date:** [May 9, 2019, 3:50pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/13 "2019-05-09T15:50:29Z")
If you don’t me asking but how are you replicating? ---
**Author:** ![jeff.earls.fr](https://www.epiusers.help/user_avatar/www.epiusers.help/jeff.earls.fr/32/16451_2.png) [@jeff.earls.fr](https://www.epiusers.help/u/jeff.earls.fr)\ **Post date:** [May 9, 2019, 3:58pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/14 "2019-05-09T15:58:37Z")
I had been battling this problem since upgrading to 10.1 in 2016 - the solution I went with which has worked to date for the last two months was to switch the recovery model to Simple. I tried everything under the sun (increase resources, have consultants analyze) to prevent the replication lock / transaction log swell with recovery model set to full. The only solution I could find was to take Transaction log backups every 15 minutes - which I why I chose Simple recovery instead. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 21, 2019, 2:07pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/15 "2019-05-21T14:07:14Z")
I have finally figured it out. Since our databases are in FULL mode, I simply created full transaction log backups every hour. ---
**Author:** ![asmar](https://www.epiusers.help/user_avatar/www.epiusers.help/asmar/32/4119_2.png) [@asmar](https://www.epiusers.help/u/asmar)\ **Post date:** [May 21, 2019, 2:26pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/16 "2019-05-21T14:26:03Z")
How big does your transaction log get at the 1 hour backup interval? And does your server take any performance impact during the transaction log backup? ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 21, 2019, 3:09pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/17 "2019-05-21T15:09:53Z")
It’s barely growing since I enabled hourly backups. No performance impact. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 21, 2019, 3:10pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/18 "2019-05-21T15:10:23Z")
Unfortunately, Simple recovery is not an option when we are syncing to AWS. ---
**Author:** ![Alexandre\_Pothier](https://www.epiusers.help/user_avatar/www.epiusers.help/alexandre_pothier/32/5421_2.png) [@Alexandre\_Pothier](https://www.epiusers.help/u/Alexandre_Pothier)\ **Post date:** [May 21, 2019, 3:16pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/19 "2019-05-21T15:16:53Z")
I would not say “unfortunately”. Transaction log backups are important!!! If you need to restore your data at some at a specific point in time, you need them. It’s way more secure than having only the last night backup available, which could lead in loosing multiple hours of transaction if data get corrupted or something. ---
**Author:** ![mnewland](https://www.epiusers.help/user_avatar/www.epiusers.help/mnewland/32/5640_2.png) [@mnewland](https://www.epiusers.help/u/mnewland)\ **Post date:** [May 21, 2019, 3:22pm UTC](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531/20 "2019-05-21T15:22:13Z")
I understand that. Just another learning curve. [Next page](https://www.epiusers.help/t/e10-production-trans-log-file-growth/55531.md?page=2)