Hi

To move a table you simply create a clustered index on the file group, if none exists then create one. If you do not want or need a clustered index then simply remove it again after the move.

The thing that I find unnecessary is...

If the move is done with the creation of the clustered index what purpose does the drop constraint with (move to Filegroup) server. You can simply drop the current clustered index and then create it on the new file group.

So could some one explain what purpose the with (move to ) part server.

Books online has this as an explanation

MOVE TO ( partition_scheme_name ( column_name [ 1, ... n] ) | filegroup | "default"}

Specifies a location to move the data rows currently in the leaf level of the clustered index. The table is moved to the new location.

But this would make sense if the constraint was not being drop but merely moved. But seeing as the index is being dropped and then recreated on the new filegroup what purpose does that statement make in this scenario...

I await your feedback....

Thanks