Fix Two Truncation Errors in a Legacy ASP.NET / SQL Server CRM (Source Code Available)

Overview I run a travel CRM built on legacy ASP.NET and SQL Server. Two screens have stopped loading with the error "String or binary data would be truncated. The statement has been terminated." I need both fixed and redeployed to the live server. I have already traced the root cause on one screen, and the full source code is available, so this is a small, well-scoped job. What I've already found On the "All Weddings" screen, the failing statement builds an in-memory result table to display the wedding list. One column, ToolTip, is defined as VARCHAR(100). The app concatenates several ID values into that column, and as our record IDs have grown over the years, the assembled string now exceeds 100 characters, so the insert fails and the screen dies. The fix is to widen that column or trim the string. The "e-docs" screen throws the same error type; I have not captured its exact statement yet, so diagnosing and fixing that one is part of this job. Environment Legacy ASP.NET application (.NET Framework, MVC era), hosted on IIS SQL Server 2014 Express Windows Server 2012, RDP admin access provided Full source code is available on the server, and Visual Studio 2010 is installed for building The SQL is generated in the application code as parameterized ad-hoc SQL, not in stored procedures Scope of work Fix the "All Weddings" screen (root cause identified above) Diagnose and fix the "e-docs" screen (same error class) Rebuild and redeploy to the live server Confirm both screens load correctly Optional: scan for other instances of this same too-short-column pattern, since more screens will break as IDs keep growing Requirements Strong .NET Framework and T-SQL experience Comfortable reading and modifying legacy code with little documentation IIS deployment experience A careful, backup-first approach on a production system Deliverables Both screens working on the live server The changed source handed back to me A short summary of what was changed To apply In one or two sentences, tell me how you would test this change and deploy it to a live server without risking downtime or data loss.