My inclination would be to move the char(7200) to a different table. Or, depending on the specific circumstances, change it to varchar(max) and force it LOB (out of the main table data).
Many places tend to have overly-wide tables because they never do actual data normalization up front. They kinda pretend to, but they don't really. They just slap an identity column (technically a column with the identity property) on every "table" and start stuffing data in, with no real forethought. This inevitably leads to a royal mess in all tables, since it is literally impossible to normalize based on an identity.
Similarly, since normalization is (supposed to be) a logical design process and not a physical one, identity property does not even exist then (the physical implementation might be autonumber or using a sequence, or indeed an identity, but that is not relevant to the logical design, it is simply a unique number at that stage).
SQL DBA,SQL Server MVP(07, 08, 09) Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: "If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them."