Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
3386 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hello, We are on Portal and moving to Tempo and would like some feedb
mjmallet
over 8 years ago
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
0
akshayan
Certified Lead Developer
over 8 years ago
Usually it's one database per Appian installation.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
peterf
over 8 years ago
We typically use a separate database schema per application (some apps have access to several schemas but they typically "own" an application schema). Not sure what you mean by "lower records process" etc. What I'm referring to is having say an application that manages dispatch, routing and maintenance of trucks and another that manages space allocation and throughput in a warehouse. I would have a "trucks" schema / database and a "warehouse" schema
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 8 years ago
We are running around 35 applications and use one database for all (MS SQL). Our Development and Test servers have their own databases, but all applications within each environment utilize the same DB.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
peterf
over 8 years ago
Are you talking about a single database instance with multiple schema, or is it just everything in a single "Appian Business" schema. We have relatively few database instances (SQL Server and Oracle) that house multiple application level schema. That works for us but obviously your situation may be different.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 8 years ago
We are currently using a single database instance with a single schema for our installation. I'm not sure if there are any best practices around schema design, or if it is completely up to the designers - but our setup works fine for us with 175 tables.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 8 years ago
Lower records process means a process that doesn't produce instances compared to others. (ex: 10 instances a month compare to a bigger process that would produce 1000 a month)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mjmallet
over 8 years ago
Thank you for your input, it really helps! :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 8 years ago
I would not worry about splitting DBs/Schemas just for size purposes. In our 175 tables many have over 100,000 rows and some over 2,000,000 - we have not noticed any performance issues so far.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
peterf
over 8 years ago
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.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel