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.
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 a Specific Merchant report in SSRS and it sent out to different merchants everyday at 8am. But the Problem is they want to receive the report only if they have Transactions on it(Contains Data)
They don't want to receive it if the report is empty.
Is there a way to restrict that in SSSRS? Please let me know.
Take a look at data driven subscriptions. They've been around since SQL Server 2005 and are pretty useful for this kind of thing. Without knowing more about your scenario, I can't explain exactly how it'll work, but I'm certain it can. Check out here for more details:
http://msdn.microsoft.com/en-us/library/ms169673.aspx
SSRS subscriptions are pretty basic - either you are subscribed to receive a report or you are not. If you want/need to add logic to that you'll need to roll your own using a console application that you can run as a scheduled task and the reporting services API.
I have development, test, demo and production systems. They all need to have the same set of reports (easily deployed via Visual Studio, multiple reports at the same time if needed) and the same set of report subscriptions. At this time I have to manually go through the sequence of up to 7 steps in web UI for report manager to deploy or modify each subscription on each system.
Is there a way to automate/improve creation/modification of report subscriptions? I use SSRS 2008.
I've cheated in the past and manipulated the reporting database in SQL Server, you could dig around in there and see if you can figure out the records you need to add.
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