msmithson (3/14/2014)
My company recently migrated to new hardware. The decision was made to create a database file per core per filegroup so now the database is spread across > 80 files. All of these files reside on one RAID10 volume. I cannot find any evidence online to support this configuration for a user database (only tempDB and even then its 1/2 to 1/4 the number per core). Is this configuration ok or is there something we should look at specifically to see if it is causing performance issues?
Having 80 files for a DB is not a good design. It will have a negative impact on the performance and make administration complex.
--
SQLBuddy