I would like to know in order to use the Report Builder at the user system, What kind of licencing model we require, If we have one SSRS server (SQL Server licence) and all the users can download report builder?
What is the licencing model to use the Report Builder? It is SQL 2008
When you install Report Builder you should see the licensing terms. They stated that you are free to use this product in conjunction with validly licensed SQL Server. Look for the words: "You may not use this supplement if you do not have a license for the software."
Basically, if you or the user that is going to use this is licensed for SQL Server, then you can use this.
Sql Server Developer Edition is very very cheap per seat (approximately $50 US). When I've run into scenarios where there is some user or analyst who doesn't need access to anything in the world but a development SQL Server, I get a copy of that license.
Related
How can I implement Anonymous Access for Reporting Service with SQL 2012?
Why on earth would you want to allow anonymous access to your report server in (I assume) a production environment.
If by 'anonymous access' you simply mean that want all users in your domain to be able to access the reports you publish to the report server (I'd think about this also - obviously I don't know where you work or what reports you are producing, but do you really want very junior staff seeing profit/loss accounts for example?) I suggest you start by reading the documentation here.
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
I have an Access db file, and I need to slice and dice the data for various reports that my boss wants.
Is Microsoft Reporting Services a tool that is appropriate for this kind of activity?
If so, would I import the Access data in SQL Server, then the reporting services is a tool that works on SQL Server, allowing the report builder to build custom reports?
SSRS is great for what your trying to do if you wish to stick with Micrsoft tech.
SQL Server Express Adv edition comes with report server. There are plenty of guides out there for install / set up but once going you can use a little application called Report Builder that lets you design the layout of the reports themselves.
Reporting server esentially generates reports from templates you produce in report builder app.
The free edition of report server that comees with SQL Express Adv can export reports into three types, word files, excell or PDFs and does a very good job at it. It also exposes a webservice with a whole myrad of web methods thats very very usefull. ASP.Net also has a control which you can drop into your apps which will render a report.
So in short, yes :)
Hope this helps.
Two interfaces of Reporting Engine are possible:
sql based for sql based user
non-sql Based interface for normal non-sql friendly users
Database is very large so how do I go about thinking about 2) option that is Non-sql based interface
How would it be ?
If you're using SQL Server 2005 or higher, you may want to consider the ReportBuilder supplied as part of Reporting Services.
You just need to build a 'business friendly' schema (known as a 'DataSource View') then auto-build a Report Model on top.
The users just connect to the Report Model using the Report Builder tool and they can create their own reports.
If you already have SQL Server, then the additional costs would be minimal.
You need an easy way to build SQL queries. Look at the wizards in all the desktop databases, but something that isn't paged might be more intuitive, e.g. http://ruleeditor.googlecode.com/svn/wiki/NSRuleEditor_Tiger.png (not affiliated)
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