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
Related
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.
I would like to know the easiest and fastest way to retrieve data from SQL Server 2008 R2 via Sharepoint 2010.
I am new to sharepoint but have been able to create an external content type using Sharepoint designer which connects to the database in SQL Server but I have not been able to use the business web chart to relay the data gotten from the database.
I want to relay information from a customer service database into sharepoint and want it to be consistent.
Is this the best way to go about it or is there a better way?
Many thanks for your usual cooperation and response.
Cheers,
Tunde
Your best bet is SQL Server Reporting Services, which will need to be installed in Sharepoint integrated mode. It does not have to be 2008 R2, it can be 2008, and the good news is that if you run reporting services on the same server as your SQL databases, you're already licenced for it.
Take a look at http://www.bidn.com/ for more answers, or ask questions using the #SQLHelp tag on twitter for SSRS, or #SPHelp for sharepoint
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.
I'm looking to implement SQL Server Reporting Services as our standard reporting platform in our company. We were trialing Crystal Reports, but alas it seems to be plagued by issues.
SQL Server Reporting Services looks to be a great product, but I have a concern or two.
I have some existing web apps in ColdFusion, and the backend is in MySQL. If I move forward with SQL Server Reporting Services, how should I set up my environment? Is there a JDBC connector or is ODBC the only way to talk to this?
How does it integrate for the user? Will I need to re-authenticate the user to view the reports? Will I need to put a link in ColdFusion to link to the Reporting Services system? Is there a way to make it seamless for the user?
Should I port all the backend to SQL Server to fully leverage the SQL Server platform? Should I convert my existing apps to ASP.NET, and make the entire platform SQL Server / ASP.NET?
It's not too bad in the fact that the existing apps / MySQL aren't of a size that is too big to port. So I guess just looking for some best practice advise to see if its okay to use the reporting services component on its own, or if I'm much better to consolidate everything into a Microsoft solution.
I think it'll be easier than you think!
Reporting Services will happily pull reports from any OLEDB or ODBC source, and MySQL has ODBC drivers, so there's no problem getting at your data through an SSRS report.
You can set up the authentication in a number of ways. If your users are already authenticated in your Windows domain, this will be easier:
SSRS needs to know who is viewing the report. It will allow anonymous viewing (if you enable it; it's off by default), but if you're using IE and are logged in to the same domain as the IIS server, it's completely transparent
SSRS can then use this identity to connect to the data source, or it can use another identity. This is configurable per report or per data source.
One thing you could do is embed your reports within iframes in your coldfusion pages. This would make the whole thing seamless. The reports are accessible by sending an appropriately formed URL to the server, so it's quite flexible.
As for changing everything to ASP.NET, you'll really only get benefits from that if you ever need to write (and integrate with) your own code to manage the reporting server, or write custom extensions (data providers, delivery extensions and the like), but in my experience this is so rare as to be not worth considering. Go with what you have for now.
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