Multiple schema best practice clarification

Certified Lead Developer

docs.appian.com/.../appian-cloud-database-administration.html

Does anyone have additional context on the reasoning behind these recommendations?  My client has hard data segregation needs and plans to use multiple schemas to address them, but we want to know more about what problems we might expect to run into.  We're using the cloud database.

The biggest issue reported to me so far had to do was a problem around using compare and deploy to update stored procedures (ones that reference multiple schemas), but they found a manual workaround to mitigate that issue.  I'm curious if there's any other notable issues that can be expected or if there's any loss of other capabilities we're unaware of at this time.

Thanks

  Discussion posts and replies are publicly visible

Parents Reply Children
No Data