Should SSRS 2008 be on a different machine to the database? - reporting-services

I have seen recommendations for installing SSRS 2005 and it states that you should separate it from the database engine that hosts the data sources for your reports, that you should not install them on the same server.
Is there any equivalent documentation for SSRS 2008 that provides guidelines/best practices for installation? I am assuming that the same holds true for SSRS 2008 as it did for SSRS 2005 but have not been able to find any documentation on it.

I cannot point you to any specific documentation. However, I have visited the Microsoft testing labs in Charlotte, NC several times over the last 5 years to test SQL Server 00/05/08 SSRS based applications and was provided sage advise by the MS SQL experts.
They recommended that no other applications be run on the database server other that the SQL engine. This included SSRS. This was not easy at all to accomplish in the SQL 2000 product but become much more digestible with the scale-out options in SQL 2008.
It really does depend on the load profile of your application. You need to test and quantify the engine load verses the reporting load.
One consideration is that the memory and CPU consumption of SSRS '08 is significantly less that '05 due to re-designs in the reporting engine as confirmed by Microsoft and our testing.
My advice would be to load/stress test your application and adjust your hardware and deployment strategy accordingly. Using Microsoft Testing Labs for this is great environment because they have tons of hardware to test multiple scale scenarios to determine the options for your target deployment scenario.
I hope that provides some insight.

This series of web pages from the SQL Server Customer Advisory Team provides recommendations for SSRS 2008
Reporting Services Scale-Out Architecture
Report Server Catalog Best Practices
Reporting Services Scale-Out Deployment Best Practices
Reporting Services Performance Optimizations

Related

SSRS 2014 Data Driven SubScriptions not available

I am currently looking into Setting up Data Driven Subscriptions on our 2014 Server, however when trying to follow the instructions in the tutorials I can find I'm running into a roadblock, which is as simple as I just don't see the option for Data Driven Subscriptions anywhere! Is there a service or some setting that I am missing ? I have complete Admin access to the server & the Reporting Server site.
Thanks
Data Driven subscriptions are only available on Enterprise and Business Intelligence editions of SQL Server 2014:
https://msdn.microsoft.com/en-us/library/cc645993(v=sql.120).aspx#Reporting
I have often run into this limitation, and it has kept me from developing data-drvien subscriptions many times. The cost difference to upgrade to SQL Enterprise usually kills the value of this feature. One easy work around is to have the subscription run regularly, but change the data in the report depending on the recipient.

SQL Server 2012 SSRS Over AlwaysOn Availability Group

I am setting up SQL BCDR for my project using SQL Server 2012 Availability group. I could successfully implement it for my database. But I have SSRS, which I want to include in the Availability group.
What is the best approach for this. Ideally, I would want my client to connect to the reporting server using the listener name or a common static name, so that during fail-over the client doesn't need to change anything.
Any good read in terms of configuring SSRS with AlwaysOn?
Thanks
This is a very common situation but certainly achievable with the built scalability feature in SQL Server 2012 (AlwaysOn Availability Groups). There are few limitations and things to consider when planning on using SSRS with AlwaysOn Availability Groups. Please refer to this link for further detail. http://msdn.microsoft.com/en-us/library/hh882437.aspx

SSRS vs. any other Technology for integrating to current Web Application

I am here to get the opinion on Reporting Services vs any other technology suitable for Reports.
Current Environment - BIDS 2005, SQL Server 2005, C# 3.5, VS2008.
requirement -
My Client needs to integrate the huge reports into current existing Web Application.
1) The Technology should be able to handle large number of users.
2) All clients are external, so they can review the reports anytime.
3) Caching of parameters and the report should be possible.
4) The Report Viewer is better or SOAP API is better considering Reporting Services.
5) Charts can be used - good Visualization.
All opinions are welcomed.
Thanks in advance.
The most honest answer you're going to get is "it depends." What is your familiarity with with SQL Server Reporting Services? What's your familiarity with the other tools? Do you have a DBA who is familiar with SSRS? There are way too many factors that play into this to give you a clear answer.
Admittedly I'm biased but I think you should look at Windward Reports. It's a lot easier and faster than SSRS and you design the report in Word, Excel, or PowerPoint so you can do a lot more.

MS Access + OLAP

I have lot of data in MS Access, and for analysis I need tools. Might you suggest any tools for data mining and analysis (OLAP)?
Support for Access (and other various non-SQL Server data sources) will be included in the upcoming SQL Server 2008 R2 release (this release is focusing on self-service BI). You can follow how the project is progressing at http://blogs.msdn.com/gemini.
It depends on your data volumes the the complexity of the relationships that you want to investigate:
(1) Moderate volumes with low complexity relationships - use queries, pivot's graphs and reports in ms-access.
(2) High volume and or high complexity relationships - consider up sizing to SQL server and using the more grown-up data cubes (OLAP), stored procedures etc.
A possible solution can be Excel 2010 using the new Power Pivot Add-on.
It really depend on the type of analisys needed.
Federico
I guess your best bet would be to import your data into SQL Server using SQL Server Integration Services - should be pretty straightforward and painless.
Once in SQL Server, you have the Analysis Services at your disposal which give you all these capabilities for OLAP analysis.
I don't think there's much for MS Access directly.
Marc
If it is not too much data, import it into Excel and use the privot table functionality.
If it is too much for that then SQL Server is the way to go.
An alternative OLAP solution is to use icCube to connect directly to your MS Access file.

What are the limitations on using SSRS with SQL Server 2005 Express edition?

I found this extremely old document which appears to say that many of the web client features are not availiable when running on express edition--scheduling, subscription, etc--as well as no access to the report builder. Is that information still current, and are there any other features which are unavailable?
Subscriptions and scheduling are indeed absent in both MSSQLEx2005 and MSSQLEx2008, but I have never found this to be much of a problem. The underlying platform has a scheduler and the web service will do all the rendering, so you can recreate the missing elements without too much trouble.
The report builder is also absent, and this is non-trivial to replicate. You could always install SQLEx locally and let them use BIDS. Or you could stop being cheap. It's pretty good for free.
I recommend you use SSRS2008 rather than 2005 because it no longer requires IIS, and there are several sexy new capabilities in the report engine. In particular it now supports flow-based rich text with inline fields for mail-merge type reports.
Compatibility is excellent but some applications reject a newer database engine version. If this is a problem, continue to use SQLExpr2005 for the database.
So, are you saying that A) SSRS 2005
requires IIS whereas 2008 does not,
and that B) SSRS2008 is backwards
compatible with a SQL2005 database?
(It sounds like you might be saying
that SSRS 2008 could be used with
somebody running 2005 DBs
Yes, I am indeed saying that
SSRS 2005 requires IIS whereas 2008 does not
SSRS 2008 is backwards compatible with a SQL2005 database
SSRS 2008 could be used with somebody running 2005 DBs, or even 2000 DBs.
You can use SSRS with any database server for which ADO.NET drivers are available, including Oracle and MySQL.
I've caught somewhere the idea about rich text in SSRS 2008.
As I see it will allow me to make such static text
"Some test with some text in bold and some italic text"
with a single text box which was impossible in RS 2005. (even don't know good way to make it there)
You wrote it doesn't require SQL Server 2008 to be installed.
What about IDE for reports development ?
Looking forward with big hopes for SSRS 2008,
thanks for attention in advance,
Alex