This question was
closed
by
nidheesh.r.pillai for the following reason: The question is answered, right answer was accepted
asked
Is it good practise to use Primary filegroup for all purposes?
Currently all our SQL Server objects are created on the PRIMARY filegroup (even on Production). I wanted to know what are the advantages/disadvantages in such a configuration? Is it a good practise? Is it better to employ different filegroups for different databases?
The default is primary and works for most all situations. Some situations warrant the creation and usage of secondary file groups. Most of the time I have encountered secondary file groups is for archiving data into secondary read only file groups or for separating indexes. Advantages of a single primary file group is it makes maintenance easier, disadvantages for very large databases is you have to restore the entire database versus being able to perform piecemeal backup and restores.
15 People are following this question.
