Hello, We are on Portal and moving to Tempo and would like some feedb

Hello,

We are on Portal and moving to Tempo and would like some feedback on databases and what other organizations are doing.

Is it better to have one dedicated database per process? Or to have one database for multiple processes?

Or maybe have one database for the "low records" processes and dedicated database for the "higher records" processes?

Thanks
MJ


OriginalPostID-166601

OriginalPostID-166601

  Discussion posts and replies are publicly visible

Parents
  • Agreed that size is not likely to be a driver. For us the issues are external reporting on the application schema, security, portability and maintenance. Questions like does the app support multiple LOBs or just one are likely to come into play.Of course this discussion is predicated on the schema being "owned" by the Appian application. We have applications that also connect to data stores that are owned by other applications and we typically don't park our Appian tables in their schema. As csteward implied, it's a question of figuring out what is right for you business and application portfolio, there is no one size fits all solution.
Reply
  • Agreed that size is not likely to be a driver. For us the issues are external reporting on the application schema, security, portability and maintenance. Questions like does the app support multiple LOBs or just one are likely to come into play.Of course this discussion is predicated on the schema being "owned" by the Appian application. We have applications that also connect to data stores that are owned by other applications and we typically don't park our Appian tables in their schema. As csteward implied, it's a question of figuring out what is right for you business and application portfolio, there is no one size fits all solution.
Children
No Data