You are not logged in.
Dear users of this forum,
we are pleased to inform you that we will be updating the software behind this forum in the near future.
Existing posts, users and categories will remain untouched.
Important:
We will keep you informed in the pinned thread.
Kind regards,
Your ReportServer Team
Liebe Nutzer dieses Forums,
wir freuen uns, euch mitteilen zu können, dass wir in naher Zukunft die Software hinter diesem Forum aktualisieren werden.
Existierende Beiträge, Nutzer und Kategorien bleiben weiterhin bestehen!
Wichtig:
Wir halten euch im angepinnten Beitrag auf dem Laufenden!
Mit vielen Grüßen
Euer ReportServer Team
Pages: 1
Please guide us on how to cater the high availability of ReportServer. Here do we need to have a separate load balancer also.
If there any documentations related to that, please share with us.
Thanks & Regards
Nayana
Offline
Hi Nayana,
the database must support high availability. All metadata reportserver needs is stored in the internal database: reports, users, permissions, etc. The issue left is the availability of your application server. There might be strategies already in place. A good way to achieve this is to have a redundant application server that takes over in case the main application server is down. These are regular procedures your server provider should be well aware of.
Load balancing is not supported internally. To implement load balancing you have to divide the load manually (IP address ranges?). Two instances of reportserver can run on a single repository with some exceptions, e.g. as long as you do not allow scheduling from more than one instance.
Regards,
Eduardo
Offline
Just to get more clarity, if we have 2 reportserver instances and for scheduling, we need to refer only one instance, but not to both. Is that what you mean? Please guide.
Thanks & Regards
Nayana
Offline
Hi Nayana,
if you have 2 reportserver instances using the same repository (i.e. the same internal reportserver database), you have to disable scheduling on one instance. You may disable it using the terminal command "scheduler daemon stop". Please check here for more information: https://reportserver.net/en/guides/conf … Scheduler/ and https://reportserver.net/en/guides/admi … scheduler/
Regards,
Eduardo
Offline
Thanks for the information
Thanks & Regards
Nayana
Offline
Need one clarification. If two reportserver instances are connected to one matadata repository, may i know the exceptions involved.
If two users are trying to modifying one object, what will be happened? Please guide.
Thanks & Regards
Nayana
Offline
Please guide on concurrency issues which may come across.
That is, If two reportserver instances are connected to one matadata repository, may i know the exceptions involved.
If two users are trying to modifying one object, what will be happened?
Thanks & Regards
Nayana
Offline
Hi Nayana,
last commit wins. Pls. make sure that you do not concurrently work on the same object if you want to avoid conflicts. That applies always its the same if you do use a single instance and two developer work on the same object. If the developer A changes it and developer B changes it and they both loaded the same initial state the last commit wins.
As i said it is a good idea in order to avoid daunting conflict resolution to not concurrently work on the same object. Regarding content it makes sense to have a single developer work on a single report.
wbr jan
Offline
Pages: 1