|
Hi all, just an easy question/need this morning. I'm looking for informations pointing out that a data source shouldn't be too far away from SSRS. I have a request to create additional data sources that will point to several remote locations. I have a gut feeling that this isn't best practice at all. Regards Dirk
(comments are locked)
|
|
Hmm...frankly speaking I do not know what to answer precisely ;) But it is definitely not the best option unless it is the only one you have. It could mean if there are several remote locations with reports of large data sets (simultaneous run), you could be having lots of performance, timeout, Logon issues etc. It can even make your server slow for the local DBs. So this becomes sort of Capacity Planning. If you have an ultra fast network, multiple network routes, multiple network cards, a beefy server, then you may get away with this ;) But one should ask why there is a need for that? Less hardware resources OR someone put an idea to have a centralized Reporting Server for all remote sites for centralized management? Well' we already have de-centralized SSRS in place. But now there is the idea of few new reports which need some KPIs from other locations as well. So, instead of consolidating the data to one location and get the data from reporting there, the report itself should use several data sources, querying the locations directly and view the result.
Jul 19 '12 at 11:36 AM
DirkHondong
I do not see it as a good idea. What if any of the remote site is down? Moreover, KPI reminds me of SharePoint and Excel more ;)
Jul 19 '12 at 12:36 PM
Usman Butt
(comments are locked)
|
What are these additional data sources exactly? Are they shared data sources?
Yes, they are. Or better: will be
So the problem is the remote sites? They are not in the same data center and you are worried of the issues may arise due to Network Latency?
That is right. And I do not have the information tight now how the query will look like, how many data will be selected etc pp.