I am not sure how a 'table' change requires updating/modifying all stored procedures/views/functions/etc... Do you mean to say that the old table is no longer used - and a new (different name) table is now being used?
If so - then how sure are you that all of the columns being referenced by the views/procedures/functions in your report database have not also changed? Is this new table a copy of the old table with all of the same columns?
I am assuming that the reference to the old table is something like: DataDB.dbo.OldTableName
To prevent this kind of issue in the future, you need to start utilizing SYNONYMS from the report database. This will allow for easy updating of the synonym to reference a new name (or even a new database with the same structure).
CREATE SYNONYM DataDB.TableName FOR DataDB.dbo.TableName;
Now in your code, instead of using 3-part naming you can use the synonym:
SELECT ... FROM DataDB.TableName
And if the name of the table changes - all you have to do is:
DROP SYNONYM DataDB.TableName;
CREATE SYNONYM DataDB.Table FOR DataDB.dbo.NewTableName;
And now all of your code is referencing the new table with no additional changes needed.