This content has been marked as final. Show 7 replies
Yes. Unless you absolutely require, it's generally suggested to limit one db per app. (Although you've no choice for ASO :) ) due to the possible locking reasons!
Yes, you can have more than one database in Essbase application. Essbase app can consume max 2 GB memory hence Hyperion recommends to define only one db in an application only. There are other issues also if define multiple db in an app.
Atul Kushwaha wrote:Please note those are the restrictions of 32bit, 64bit does not have these restrictions.
Essbase app can consume max 2 GB memory hence Hyperion recommends to define only one db in an application only.
Also if you look at planning applications they can have more than 1 db per app.
1. Firstly, we can make a 32 bit consume more than 2 GB .
Pls refer "Enabling Windows 4 GB RAM Tuning" topic
2. And adding to John's find information on 64 bit
Sandeep Reddy Enti
There's an interesting question -- does 64 bit Essbase ever hit a memory threshold with mutliple databases active in one application?
I can think of some other downsides beyond that technical limitation:
1) You have 15 databases, all starting when the app starts. You use one -- those 14 are going to chew up RAM you could do other things with.
2) Stopping the app/starting the app is going to take a lot of time.
3) It's hard to navigate them. <-- That's pretty weak.
And I guess that's it. If that imaginary 15 databases under one app didn't break a 64 bit limitation, whatever that is, what else would make you not want to do it? 32-bitness and general tidiness is why I don't do it.
We can create one or more databases for an application.
But recommended is only one database for an application. The reason for this is that when you restructure a database, the entire application is locked and you will not be able to perform any other actions on the application or dependent databases.
During processes, Analytic Services logs messages only at the application level. There are no database-level process logs. Multiple database logging makes it difficult to effectively interpret the log. Server resources are more balanced.
This rule is an exception for the planning and currency databases.
Single Application/Database structure allows for a more organized layout and design and also allows for better data and security management.