MS SQL Database bloated and diskspace

I have a very old database  on an very old server

The database has a table that has gotten bloated and is eating up drive space.

When I try and delete rows from the table I get a tempdb out of space

I cannot add drive space.  

What are my options?
Larry Bristersr. DeveloperAsked:
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.

Vitor MontalvãoMSSQL Senior EngineerCommented:
Check if you can shrink the transaction log files to free some disk space for the tempdb.
Also check if there are non database files in that disk that can be deleted.
0
65tdRetiredCommented:
As above try shrinking the database files as well.
More info on tempdb:
https://technet.microsoft.com/en-us/library/ms190768(v=sql.105).aspx

Are the DB files on the OS drive?
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
Scott PletcherSenior DBACommented:
Agree with Vitor, you can probably get some disk space by shrinking log files.

Still, it's odd that tempdb would run out of space, unless you have some type of replication, CDC, snapshot, etc., on the table.  Or the db log file is on the same drive as the tempdb file(s) and the tempdb files are growing for a different reason.

If there is a temp-using process on the db, temporarily (or permanently?) stop/disable the activity that requires tempdb space, then try the deletes again.  

If you're deleting lots of the table, it's usually much more efficient to write the good rows to another table, TRUNCATE the original table, then copy the good rows back in.
0
NerdsOfTechTechnology ScientistCommented:
First, I recommend to troubleshoot the error:

https://technet.microsoft.com/en-us/library/ms176029(v=sql.105).aspx
0
Larry Bristersr. DeveloperAuthor Commented:
Thanks
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
Databases

From novice to tech pro — start learning today.