July 6, 2013 at 10:54 am
Hi friends,
I have sql server 2008 R2 enterprise database. I have compressed tables and then created indexes for the same table. Then compressed the same indexes on that table. When am trying to shrink that database, the session is continously in suspended state. After 2 days even 100 MB is not shrunk. Now the available free space of the database is 600 GB. Kindly guide me how to get rid off this issue.
Thanks in advance.
July 6, 2013 at 1:00 pm
Suspended means it's waiting for something. Check what the shrink is waiting for.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 6, 2013 at 1:43 pm
Hi Friends,
Nothing is running in the server other than shrinking, as its weekend we have stopped our applications & we have even restarted server for the activity. Eventhough it didn't help. Is there any other way to find why its suspended.
We are having 64 GB RAM, we are using SQL server 2008 R2 Enterprise Edition SP2.
OS : Windows server 2008 R2
Kindly guide what can I do further.
Thanks in advance.
July 6, 2013 at 2:23 pm
Check what wait type the shrink process has. It's a SQL Server process, it'll show in the DMVs like any other running session and a suspended status just means that it's waiting for something. Check what its wait type and wait resource are.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 6, 2013 at 2:25 pm
Hi Friends,
Thanks. After dropping indexes, shrinking of the database is in runnable state.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply