question

Hello, I do understand all the negative side of dbcc shrinkfile (that it causes severe fragmentation, single threaded, would take a long time, never run autoshrink, etc). We have a necessity to shrink our mutli-terabyte DB. Our DB consists of multiple datafiles. Even though I see general recommendation from Microsoft to run shrinks one file at a time to avoid system tables blocking, I took risk, went ahead & ran dbcc shrinkfile on two data files at the same time in parallel to cut down total time to shrink all DB files Now the two shrinks threads are blocking each-other on system tables and are stuck for more than a day. We had same situation couple times previously and 1. we tried killing one of the shrinkfile SPID - rollback was never progressing/complete and was stuck. We re-started SQLServer, and the DB went to suspect mode. We had to restore the DB from the backup 2. On another similar occation, we just recycled the SQLServer without trying to kill one of SPIDs first, again the DB went to suspect mode and had to restore the DB from backup Is there any way that we resolve this & bring the server to a fully funcational mode without re-restoring the DB?OR just consider this as a hard lesson learnt and in future never run more than one shrinkfile at a time? Many Thanks for your input & guidance.