Isabelle2378 (5/1/2013)
Yes, based on a consultant who came in to help us trobuleshoot performance issues, the two filegroups that we have each with one 300GB file was determined to be a bottleneck and recommended that we spread the data across multiple files instead of one.
How did said consultant determine that the filegroup was a bottleneck and are those files all on separate IO paths (separate drives at least)?
When I first tried to shrink the file after it was empty, I was getting an error and after looking through SQL forums, I saw an article that stated the SQL server needed to be restarted before you can shrink the empty file.
There's no requirement to restart SQL to shrink a file. Could be there was something using data in that file and the shrink was blocked, can't tell without knowing the error.
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