• rtowne (10/16/2008)


    there is a problem (aka, bug) with this if your table has certain qualities.

    For example,

    I had a table that had a text field, so it had LOB data - I converted it to varchar(max). After this, I then tried to move it to a different filegroup as show in this article, however, the LOB data still stays on the old filegroup. If anyone else has experienced this and found a workaround other than selecting all the old data out into a new table please let me know..

    Thanks

    Robert

    That's not a bug, but a lack of control over the BLOB/statistics data placement.

    Or, from other hand :), all that Clustered Index recreation is just a hack as we were told already up above in this discussion.

    It is quite unusual requirement to move tables between the filegroups. Check out the link I gave before - that was a really nasty requirement to re-arrange ALL tables in multiple databases into new filegroups.

    But I still had to move tables with BLOB separately. Thanks god SSMS/EM generated the script for those few table in a second for me :).