Are there any specific guidelines to split up a single MDF file into multiple files for a single database. An example of a scheme that I can think of is splitting it so that one NDF file contains just indexes and another just the tables which take Insert operations, another one that has large tables etc, so the scheme would look something like:

  1. MDF containing smaller tables
  2. NDF containing indexes
  3. NDF containing larger tables
  4. NDF containing tables optimized for insert operations

Also, all these files would be on separate drives.


There are guidelines on what you can and can't do, but how to implement it in your environment depends on your architecture. Splitting things up can help, but it's not always a good idea. You need to know your I/O architecture and how SQL Server uses it so that you can plan appropriately.

Have a look through these:

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.