R
Rob Fitzpatrick
Guest
This is a gap in my understanding; I hope someone can help me understand it better. Sometimes an ABL client acquires a shared schema lock; sometimes not. So the success of online schema changes seems hit-and-miss and I'd like to be able to definitively understand it. I'm trying to help our developers automate the rollout of new builds and the accompanying schema changes to dev and QA databases. Of course, when a user already holds the shared schema lock, the schema update fails. I've searched the docs, PEG, and KB and come up relatively empty. Is there a list in a document or in someone's brain of known circumstances or code patterns that will cause a client to acquire the schema lock? (Apart from actually updating the schema...) Thanks.
Continue reading...
Continue reading...