Remember to always backup your db by simply copying it to a 'backup' folder and give it a date in the name.
Both the front end and backend, because SOMETHING will corrupt it.
(I just had a person loose his db. Yeah for backups!)
Remember to always backup your db by simply copying it to a 'backup' folder and give it a date in the name.
Both the front end and backend, because SOMETHING will corrupt it.
(I just had a person loose his db. Yeah for backups!)
Back up early and often. When coding an update, I back up the database with the date and a new letter suffix every time I think it's working with the new changes.
Once I'm absolutely sure that I have a working version and know exactly which changes are required, I port only the finalized changes into a fresh version of the production database.
Then I test the snot out of it again.
That way, I can't ever accidentally inject test code - otherwise known as "random flailing" - into production.