What's up with "The filegroup has changed. The table must be rebuilt." ?

After carefully partitioning and reloading the data into a large-ish table (almost a gig), I get this message when I try to commit the changes.

1) What does it mean?
2) Why would I even consider letting an app "rebuild" a newly partitioned table that's working perfectly and exactly how I designed?
3) How do I make this go away?

It's frightening that this is even one button click away from happening. That should not be the case for any operational database.

thanks, Tom


  • Peter_LawsPeter_Laws Posts: 202 Silver 2
    edited January 13, 2022 1:33PM
    Hello Tom,
    Since you mentioned partitioning, are you utilising a clustered index, potentially moving the clustered index to a new filegroup?
    As for expected behaviour, we'd need a fair bit more information to determine that. I'd be happy to open a support ticket for you if you'd like to pursue that.
    Kind regards,
    Redgate Product Support
    Kind regards
    Peter Laws | Redgate Software
    Have you visited our Help Center?
Sign In or Register to comment.