Sharepoint_config transaction database getting large

Sharepoint 2013 on-site is what we are running.  I have a transaction log that gets huge on over the weeken.d  Sharepoint_config is the db.   the database is in simple mode so i dont know why it is doing this.  Does anyone know what jobs a normal sharepoint setup would run that would cause this datbase to get so large on the transaction file size?
jamesmetcalf74Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Walter CurtisSharePoint AEDCommented:
Does it shrink back down at all, or stay at the large size. Check to make sure that the backups are running correctly and that the transaction is truncated after the back runs successfully.

Good luck...
Vitor MontalvãoMSSQL Senior EngineerCommented:
I will guess that it's the reindex job.
Do you have regular transaction log backups set for the SharePoint database?
Walter CurtisSharePoint AEDCommented:
Daily, but we don't retain very long.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Vitor MontalvãoMSSQL Senior EngineerCommented:
Daily, like once by day?
Depending on the number of transactions, I would recommend to run a transaction log every 15 min or at least every hour. This will help to maintain the transaction log file small.
jamesmetcalf74Author Commented:
I turned off the indexing jobs and it still grew to a large state.  I am going to monitor.  I had to shrink it again.  I will continue to monitor
balagangadhar TCommented:
Hi,
I have faced this issue and it is quite common. It all depends on how many transactions.
We cannot have any control to limit the transactions as it will create more connections which in turn locks or hangs the database. So i always use the below solution to reduce the size of file
USE SharePoint_Config
GO
ALTER DATABASE SharePoint_Config SET RECOVERY
SIMPLE
DBCC SHRINKFILE(N’SharePoint_Config’, 1)
ALTER DATABASE
SharePoint_Config SET RECOVERY FULL
GO

Now it depends on intervals to run

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jamesmetcalf74Author Commented:
Thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.