Here is some code to determine which file group your tables exist on:
SELECT o. [name], o .[type], f .[name],f.data_space_id
FROM sys.indexes i
INNER JOIN sys.filegroups f
ON i. data_space_id = f .data_space_id
INNER JOIN sys.all_objects o
ON i. [object_id] = o .[object_id]
WHERE i. data_space_id = f .data_space_id
AND o. type = 'U' AND i. index_id IN (0,1)
Moving the tables from one filegroup to the other is fairly straight forward. Personally I'd just move the entire filgroup to the new drive (rather than moving individual tables). To move the entire file group to a new drive execute the code below, stop the MSSQL Service, physically move the file from one disk to the other, then restart the SQL service:ALTER DATABASE YourDB MODIFY FILE (
NAME = YourDataFileName, FILENAME = 'X:\NewLocation\YourDatFileName.ndf')
GO
ALTER DATABASE YourDB MODIFY FILE (
NAME = YourDataFileNameLog, FILENAME = 'X:\NewLocation\YourDatFileName_log.ldf')
GO
To move just a table itself:CREATE CLUSTERED INDEX cs_YourTable
ON dbo.YourTable(YourClusteringKeyFields)
WITH DROP_EXISTING
ON [NewFileGroup]
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience