A database with a maximum record size even within sight of a feasible row size? Shudder.
But there's a lesson here for (Fr)agile development. Changing your code may be easy* but changing data is a different matter. If your data is doing the heavy lifting for a business there'll quite quickly be a lot of it and you'd better hope there's a window of time long enough for all your changes.
There's no substitute for getting the database design good enough to last for a long time and that means up-front design.
* Relatively depending on how well your automated testing works.