Forum Discussion
New columns on existing table are dropped the next day
Has anyone encountered an issue like this? I cannot find anything searching. Troubleshooting is not fruitful yet
New columns created on existing tables will disappear the next day (ie. ALTER TABLE <name> ADD <column and metadata>)
New tables created within a given DB will persist the next day/ongoing, however
Target DB is set to SIMPLE recovery. DB is in autocommit mode
Running SQL Server on Azure VM
Thankyou
New columns on existing table are dropped the next day
DataDudeError , no, never-ever heard of and believe me, it's not done by the database engine, it must be done by somewhat/someone else.
Use a DDL trigger to track the changes:
New columns on existing table are dropped the next day
DataDudeError , no, never-ever heard of and believe me, it's not done by the database engine, it must be done by somewhat/someone else.
Use a DDL trigger to track the changes:
- Thankyou olafhelper
I was leaving for a couple more days of observation before setting this up. Would be a great diagnosis mechanism
It was our own error with configuration
We had agent jobs running unintentionally, which we had not planned to activate yet in our project. Those jobs recreate some tables via drop -> select into. New tables weren't in the scope of those jobs, therefore unaffected.
Appreciate the consideration
