Skip to main content
andrewo55
andrewo55
October 30, 2025
Question

Multiple schema best practice clarification

  • October 30, 2025
  • 6 replies
  • 0 views

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

6 replies

shubhama926776
shubhama926776
October 30, 2025

Additional issues include complexity in cross-schema joins causing permission and performance problems, intermittent stored procedure failures, sync limits with large data volumes, and limited direct SQL operations in the cloud. Best to keep most data in one schema unless strict segregation is needed and test carefully.

stefanhelzle0001
stefanhelzle0001
October 31, 2025

I think that data segregation does not mean you HAVE to use separate databases/schemas. Security in Appian is mostly configured inside Appian, but not the database.

andrewo55
andrewo55Author
October 31, 2025

Agreed, I'm realizing I should have clarified that the data segregation requirements also includes restricting developers from seeing other application data.  This environment will have multiple applications hosted on it and not all developers will have access to every application or its data.

Setting up security in on the application objects to support this is well documented and supported, however on the database side our options are limited due to Appian managing the database permissions.  MariaDB supports hiding tables within a single schema, but we don't have access to the commands that let us do so on the cloud install.  Which leaves us with using multiple schemas.

harshas2775
harshas2775
October 31, 2025

For different applications different databases are alright for use and is cleaner to manage as well. As they wont have any dependencies with each other so its of minimal or no risk mostly. 

This environment will have multiple applications hosted on it and not all developers will have access to every application or its data.
harshas2775
harshas2775
October 31, 2025

Different database/schemas can make the establishing relationships difficult between two dependent tables residing in different schemas. In practice we do use different schemas for different applications on a server for better segregation and organisation. Yet for one application all tables, functions, procedures etc are easier to work with when they share the same database. 

Terms & ConditionsAccessibility statement