Wednesday, March 28, 2012

Load balancing and report servers

At the moment a client has two web servers and two reporting servers. The
first web server always uses the first reporting server, and the second web
server the second reporting server. There is no shared state, and a given
user session always goes to the same web server. Report output is displayed
via a ReportViewer web control.
They'd like to move to true load balancing of the web servers, but don't
want to pay the extra for SQL Server Enterprise licenses that reporting
server farm require.
Looking at the HTTP traffic the ReportViewer sends request to the web server
to be handled by
/Reserved.ReportViewerWebControl.axd
...with some parameters, two of which...
?ReportSession=3dobaffxgmkaduj5rukvhxvy
&ControlID=841538b0792b4b27bf84e1da251a8d87
...look as though they would provide a key to some configuration information.
If we changed to shared state, and true load balancing (such that a request
could go to any web server), what would happen when the user chose to move to
the next page in a report or output a report to PDF?
Would the web server be able to find the correct session information and
forward the request to the reporting server that originally generated the
output?
Thanks,
DukeHello Duke,
According to the documents in BOL, we did not recommand customer to use
only one reporting services on the Load Balance Node.
I may consulting the internal member to check whether you could do this or
not. Thank you!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

No comments:

Post a Comment