>Here's one of the articles: http://www.sqlservercentral.com/articles/SHRINKFILE/71414/ not sure if you need to join to read it, but joining is free.
>
>A quote from the article:
>
>"In the SHRINKFILE command, SQL Server isn't especially careful about where it puts the pages being moved from the end of the file to open pages towards the beginning of the file. This causes two problems:
>
>the data becomes fragmented, potentially up to 100% fragmentation, this is a performance killer for your database;
>the operation is slow - all pointers to / from the page / rows being moved have to be fixed up, and the SHRINKFILE operation is single-threaded, so it can be really slow (the single-threaded nature of SHRINKFILE is not going to change any time soon)."

Yes, I was aware of that reading but this was never observed on this side.