March 29, 2019 at 12:45 am
Hi Team,
We have configured Replication from Prod -- Report Server
SQL Report Server is having 40 GB memory. We have set SQL server Max Memory to 24 GB.
The report server configured to fetch the data from Prod server and we are not yet Pointed reports to Report server.
My report server hitting 95% memory some times. Is this because report server is fetching the data from prod and placing the report builder(will use buffer pool on report server) will impact some load on report server?
When we rebuild the indexes on report server , the report server using very less memory.. it is fine one week and after that again we are facing memory issue.
we cant run daily index maintenance task on report server database.
any thoughts?
March 29, 2019 at 12:37 pm
dastagiri16 - Friday, March 29, 2019 12:45 AMHi Team,
We have configured Replication from Prod -- Report Server
SQL Report Server is having 40 GB memory. We have set SQL server Max Memory to 24 GB.The report server configured to fetch the data from Prod server and we are not yet Pointed reports to Report server.
My report server hitting 95% memory some times. Is this because report server is fetching the data from prod and placing the report builder(will use buffer pool on report server) will impact some load on report server?When we rebuild the indexes on report server , the report server using very less memory.. it is fine one week and after that again we are facing memory issue.
we cant run daily index maintenance task on report server database.any thoughts?
Is the only thing running on this server the replication process? No reports are pointing to this but the memory hits 95% until you rebuild indexes on what database?
Also is this a push or pull subscription and where is the distribution database?
Sue
March 29, 2019 at 8:15 pm
Hi,
Yes, pull subscription replication and distribution database existing on report server.
We are rebuilding all databases in report server.
April 1, 2019 at 6:22 pm
Rebuilding all the indexes in all the databases doesn't help narrow things down. But with nothing other than being a subscriber for replication and having memory use build up to 95% usage every week, something is definitely wrong. It could be more statistics than index issues but that's still seeps off and I really can't say other than wild guesses. You probably need to try to narrow down more of where the issue is as it's likely not that every index in all the databases needs to be rebuilt. You would want to at least see what database, objects are using all the memory.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply