• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 384
  • Last Modified:

Shrink Database SQL 2005

I have a large database (.mdf file 597 gigs). I discovered that there were certain tables in the database that were getting loaded again and again, where in actuality they should have had a delete and reload each run. As an example there is one table that had 660 million rows and that was the result of 3 loads. The table should have had 220 million.
So I truncated the tables in question reran the ETL.
My backup file .bak appropriately shrunk to a 150 gig .bak. The .mdf remained at 597 gig, so I am running a shrink database on that file.
This step (the shrink) has been running now for over 24 hours.
My question is, that can and perhaps shoud be the case with a file this big?
Please comment.
Thanks Much
1 Solution
Imran Javed ZiaCommented:
It all depends on your server and disk subsystem. Try killing the process
that is blocking the shrink.

Be aware, if you kill any sql server routine accidentally, then your db may be corrupted.


Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now