In the previous recipe, Using Files and Filegroups, we saw that we can create a filegroup and create a table that is expected to become large and place it on different physical disks using filegroup.
But what if there is already an existing large table in an existing database that is extensively used by queries? Let's say that you are responsible for the AdventureWorks2012 database in your production environment, and there is one large table named Sales.SalesOrderDetail, which is located on the primary filegroup. You observe that the table is very large, I/O operations with a large volume of data made on this table are taking more time to be completed causing blocking issues, and other transactions have to wait for I/O operations on the same resources, resulting in bad I/O response time. You realise that there is a need to move this large table (Sales.SalesOrderDetail) containing billions of rows onto a dedicated physical disk to...