SQL 2012 TempDB Large Log File

Our SQL 2012 cluster is used to host our SharePoint 2012 DB's only. I know ou server is not setup correctly and doing my best to correct things from past admins..

Anyway I have noticed the TempDB is divided up into 6 files 1GB each but the single tempdb log file is 130GB!!!!!

Why is this and how can I correct it???
LVL 21
compdigit44Asked:
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.

Anthony PerkinsCommented:
Why is this and how can I correct it???
Either:
1.  Setup frequent Transaction Log Backups or
2,  Change the Recovery Model to Simple and give up support for point-in-time restore.

Once you have done either one of those you can then do a one time (do not even think about scheduling this) shrink of your Transaction Log.
0

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
Anthony PerkinsCommented:
Why is this and how can I correct it???
And I forgot to answer your question.  It is because the database was setup with the default Full Recovery Model and no Transaction Log backups have been done.
0
compdigit44Author Commented:
I just checked and the TempDB is set to a simple recovery model..

I have read that a large tempdb log can be caused by uncommitted changes. How can I check for this?
0
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.

compdigit44Author Commented:
I hate to say this but I made an ID10T mistake!!!

I thought my log files size was in GB come to find out it was only 120MB...... :o)

Please keep posted thought because I have a number of other question I will be opening a question for.
0
Rainer JeschorCommented:
Hi,
just some more comments:
It is common best practice to create multiple files for the temp db with a fixed size - to enforce/enable better parallelism. Normally you create a dedicated file per 1-2 cores (meaning 1 CPU Quad Core with 2 threads for each code (8 overall threads) should have 2-4 files.
Second, SharePoint is using the tempdb internally very heavily - so a good tempdb setup will increase the overall performance dramatically (or make it unusable if the SQL config is bad) - e.g. each and every security trimmed "list" (search, list elements, documents, actions ...) will be stored inside of temporary table variables inside the called stored procedures. These variables are normally stored inside the tempdb until the end of the stored procedures.  Therefore a single search or list view can have a lot of I/O to the tempdb.

HTH
Rainer
0
compdigit44Author Commented:
Great tip!!!!!!!!!!!!   :o)
0
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 SQL Server 2008

From novice to tech pro — start learning today.