SQL Server Compact Jobs and how it effects the database

I have a SQL Server 2005 Database that has grown to over 200 gigabytes in a short span of time.  The database is Microsoft SQL Server's TempDB.  Now, I don't know why or how it grew so huge but if I were to shrink the database live, would it have any adverse effects?  On another note, what could be the issue and how?  I don't see how I can pull any data out of the temp tables in the TEMPDB so right now I am at a stand still.  Please let me know, thanks!
Who is Participating?
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.

Tempdb is a global resource which is used to hold temporary objects created by users, Internal objects created by the SQL Server and row versions that are generated by data modification transactions.
So the tempDB can easily grow very large in a short amount of time when users run queries that return large results sets, create temporary tables, start a transaction in snapshot isolation, or when you rebuild indexes on large tables, etc.
I am not a fan of shrinking a DB without a good reason, however if you’re dunning short on storage space, you can shrink the temp DB and recover the space when the pertinent operation that has created the temporary objects in the TempDB finishes.

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
VBBRettAuthor Commented:
I have a TempDB that does not get smaller and it keeps on growing.  Right now, ours is over 200 gigs.  How can I stop this database from growing so much and what can I do to stop this process from happening?  Is this an internal error that keeps on flagging?
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

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.