D
dbeavon
Guest
It might be a while before our databases are running on OE 11.7. I would guess that we'll upgrade to that version around the same timeframe that the first version of OE 12 is released (we are usually a version or two behind). Insofar as "online" schema changes are concerned, it doesn't seem enough to restart all the remote ABL clients. I was wondering if anyone had any practical advice from trying to perform "online" schema changes in production, and making those changes take effect for new ABL client instances, both for shared-memory and client-server connections. While it seems acceptable to restart ABL client applications for them to pick up schema changes, it is extremely odd that we are responsible for performing admin operations on the database SERV-type processes themselves. The management of those seems like it should be the responsibility of the DBMS, and if they become internally corrupted and start generating errors - especially for new ABL client connections - then there's no way that anyone can claim the database allows "online" schema changes. Given the way in which SERV-type servers need to me manually bounced to clear out the corruption/compatibility, then in the context of schema changes, they aren't much more than glorified ABL client apps themselves. The technology isn't really client-server at all, it's more like big-client-little-client.
Continue reading...
Continue reading...