We are on BI 4.2 SP6. Database(CMS & Reporting) is Sql server 2012. We have enough memory/CPU/disk space on Production env(clustered) and separate file server and CMS server.
On BI CMS server(4.1 CMS DB+4.1 Audit DB+4.2 CMS DB+4.2 Audit DB), we have 8GB of memory, out of which 6.8 gb memory is in used as per Task manager, Virtual Machine, Virtual Processors is 2.: 1. Checking to see will there be any issues with these configuration going forward. 2. Any recommended(best practices) changes need to be done in above configuration.
Our BI 4.2 have Prod(Clustered): 96GB, Dev(24GB) memory available but checking best practice configuration for BI CMS database(separate server) which holds metadata for CMS/Audit database.
Oh, you’re asking about the space required for the database? The CMS isn’t much, maybe a couple GB. Audit size will depend greatly on the volume of usage, and it will grow with time.
Our Server Team/Database Team has only allocated 4 GB of RAM and 2 CPU cores (also virtual) for our database server. I can’t say that we have had issues with it. I also can’t say that our system might perform better if we had more.
If you go through the sizing exercises, it may recommend more memory than that, I know ours does. Documentation from the vendor isn’t good enough for us to get more though.
Thank you for the response. Currently, we are not experiencing any issues in BI platform, but since more memory(7GB) is been consumed at CMS server level. Checking on information on how to avoid future issue if allocated memory(8GB) is fully be in use.
We also have only 4GB allocated to the CMS db and FRS server. Yes I know SAP does not recommended running CMS and FRS on the same machine but it’s working pretty well for us and they are on separate drives.
consistently uses about 3.6 GB.
I think you are saying that you are running SQL Server 2012 with CMS and Audit databases, on the same machine that the BO CMS service is running.
Best practice would be to have a dedicated DB server.
SQL Server will consume as much RAM as it has available, so that it can buffer ‘hot data’ to memory for performance. Therefore your CMS is clashing for memory resource with SQL Server.
This obviously depends on how much work your system is seeing, and performance may well be acceptable as is.
(BOB member since 2002-08-29)
(BOB member since 2002-08-15)