D
dbeavon
Guest
Production releases aside, I would think that other people would encounter this stuff in their day-to-day software development activities. When you do a database change in the development or testing environment, do you always restart the entire database as well? Or maybe you don't use client-server connections? When working with the legacy "shared memory" connections, we don't normally have as many troubles doing "online schema changes". Today we wasted a lot of time trying to figure out why our code was failing in one environment and not the other. It had nothing to do with the custom code, or the custom schema. Everything was deployed properly and successfully. That deployment was done more than a day ago. The difference came down to the fact that one database was restarted somewhere along the way and not the other. Bouncing the database is not one of the first things you think to do when your programs aren't running properly. These so-called "remote servers" seem picky about their schema. And, as near as they are to the database itself, they don't wan't to retrieve fresh schema without a full database restart. It doesn't make sense!
Continue reading...
Continue reading...