I'm having a strange issue in one SQL Server 2008 R2 I admin. Three days ago, a major renaming on the columns of a table was made due to a development. After the columns where renamed, the change was manually propagated to any DB dependencies and after that to the program making use of the server. Yesterday evening I was using the program and everything was working correctly. I even made inserts on the table using the new program interface.
Today, the boss was ranting because some important report (sp that depends on this table) was throwing an error. The report was changed to use the new column names, but when I got to the table, it was reverted to it's previous state (!!!) not only on one DB, but also on a 2nd one they have for another company (!!!!) The procedures still are correct (new development) and even the data I inserted after the change is in the table.
It never happened to me in other server. But I can remember just some months ago something similar happened. I'm really scared.
What would make a server revert table design changes in two different DBs after three days of normally working and several backups made?