Examples in many sources, including BOL, label filegroups with no particular meaning (e.g., ❋ Unknown (2008)
Indexes, data, should be on separate filegroups and filegroups should be spread on physical disks. ❋ Unknown (2006)
Second, don't do this with a large database - the possibility of multiple files in the filegroups on a complex database is high, and you might not get them all. ❋ Unknown (2010)
As you mentioned, it does have it's limitations so the choice of storage isn't straightforward. e.g. Database Mirroring isn't supported and database snapshots don't work with FILESTREAM filegroups. ❋ Unknown (2010)
Handy script to get the filegroups and other information for partitioned tables ❋ Simons SQL Blog (2010)
But all filegroups are present in a single SAN disk. ❋ Unknown (2010)
This little script gives you the filegroups for each partition in a partitioned table. ❋ Simons SQL Blog (2010)
A full, or differential, backup can be taken of one or more filegroups or files. ❋ Unknown (2009)
Identify the filegroups containing the full-text indexes ❋ Unknown (2009)
Other best practise includes splitting tempdb into several files, putting data and log files on separate disks, placing clustered and non-clustered indexes in separate filegroups (on different disks), keeping statistics up-to-date, etc. ❋ Unknown (2009)
Now, the DifferentialBaseLSN of the file in the Primary filegroup is 28000000021500037, while the DifferentialBaseLSN of the files in the secondary filegroups remains unchanged at 28000000017700067. ❋ Unknown (2009)
Split the Search database tables on two different filegroups, and host the corresponding files on different sets of disks, to keep the crawl and query loads segregated and minimize I / O contention. ❋ Unknown (2009)
The author does not neglect to cover the area of data management, pointing out the relevance of proper placement, separation, and sizing of database files and filegroups, with particular emphasis on some of the default behavior (such as Autogrow settings or initial tempdb size), which suitability should be carefully considered, as well as requirements necessary to take advantage of the instant initialization functionality introduced in SQL Server 2008. ❋ Unknown (2009)
Exclusion of indexes on read-only filegroups in IndexOptimize. ❋ Unknown (2009)
FILESTREAM filegroups can be on compressed volumes. ❋ Unknown (2008)
When you are using failover clustering, the FILESTREAM filegroups must be on shared disk resources. ❋ Unknown (2008)
