We have a new 2016 report server. It is supposedly the Enterprise Edition but Data Driven Subscriptions are not available in our PROD database but they are available in our TEST server.
I know that versions lower than the Enterprise Edition do not have Data Driven Subscriptions but our Operations department says that the servers are set up the same.
Unfortunately, I do not have access to check out the server edition (or much else) myself so I can't say for sure that the PROD server is the Enterprise Edition. Our Ops guys haven't done much with SSRS - I had to tell one guy where to set up the e-mail server so the e-mail Destination appeared.
TEST SERVER with data driven subscription:
Is there any reason, other than not having the Enterprise Edition, that could make the Data Driven subscriptions to not appear? Is there a setting or an option that needs to be checked during installation?
There is no setting (as far as I am aware) that would disable the Data Driven Subscription option from appearing on your subscription window by default.
Simple Select ##version in SQL Management Studio against your prod environment and compare it to your test environment.. that should tell you what version straight away.. or connect to the reporting server instance and then look at server properties.. Edition., It's got to be the version!
Related
We have assumed maintenance of a legacy 32bit application. I installed TFS 2008 to use in maintaining the project.
We will never use reporting or sharepoint. I cant create a project because of issues with SSRS.
(The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on OHSENSS801. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the SQL Server Reporting Services site. )
How can I disable reporting and sharepoint in TFS 2008?
Thank you.
Unlike TFS 2010 and above version, you have to install the SharePoint components for TF2008.
TFS2008 is a very old server version and out of support for a long time. You could use TFS2010 instead, the SharePoint is no longer a prerequisite when you install TFS2010. You can go for TFS2010 Basic Configuration which is the most compact TFS installation possible.
In Basic Configuration, SharePoint and Reporting Integration will not be possible. It will install and configure Source Control, Work Item tracking and Build Services only.
Highly recommend you to move to a newly versioned TFS server. If you insist on using TFS2008, you could try to troubleshoot the configuration of SQL Server Reporting Services. Details please refer this thread in MSDN: SQL Server Reporting Services is not configured correctly
About how to remove Sharepoint and Reporting Services from TFS, you could go through this question. However, afraid removing these components, you will still not able to create team project. After all, if it will work, there is no need to be a prerequisite for installing TFS2008.
I am trying to configure reporting services in TFS 2015, but there no Edit link visible on TFS Administration console.
I have upgraded server from TFS 2010 to TFS 2015.
.
Thanks in advance
Please make sure you have configured below settings before adding a report server.
Q: What kind of report server can I add?
A: You'll need to add SQL Server Reporting Services to provide a
report server for TFS. This can be added to the SQL Server instance
that is supporting TFS, or to a different instance.
Q: What permissions do I need?
A: You need to be a member of the local administrators group on the
server, the Team Foundation Administrators group in TFS, and the
sysadmin group in SQL Server, or have the equivalent permissions.
Also note:If you installed TFS on a client operating system, such as Windows 7, you can't add reporting as described here, because it isn't supported on client operating systems.
I am using a SQL 2008 R2 Express edition. Now that its time to deploy, I need the Standard edition sql server. The database is simple with a million records of addresses which could be queried using google maps with a zip code. Also, it will be storing account information like username and password which are limited(maybe 30-40 accounts). It will be hosted in one server only and once accessible using those account information(not a public web site). I am planning to setup SQL Server authentication. Can any one tell me if 2008 should be enough for my purpose or do I need 2008 R2 for some specific reason? Also 2008 R2 is really expensive compare to 2008. 5 CAL license is enough for me as I will be the only one handling the database. Since, this is my first production deployment, I am not sure what to chose.
Please let me know.
I have been working for a client who run SQL Server 2008 in their live environment. I had been working onsite for a period but now work from home. However, due to security, I cannot connect to the live setup, I can only connect to a test server. This server runs SQL Server 2012. I script any code and send it to the office for someone to deploy. The problem I have is I am now doing some reporting services work. They are only pretty basic reports, tablix controls, nothing fancy. Is is possible to build on 2012 and deploy to 2008? Can I do something with the .rdl file to make this work or is it not going to be feasible?
Thanks in advance
In the Properties of the ReportServer Project in Visual Studio you can set the target server version.
Right click the Project in the Solution Explorer pane and set the TargetServerVersion Property to the required version. This works for reports SQL Server Reporting Services 2008 onwards. The designer will then manage what features are available to avoid using features from a later version of SSRS.
The .rdl files are nicely formated XML. You can use your favorite diff tool to compare reports generated in either version of the tool.
I'm pretty sure that Microsoft doesn't support moving a newer RDL to an older version server.
There were huge changes to the .rdl format between 2005 and 2008, moderate changes between 2008 and 2008R2, but I haven't really looked into 2008R2 versus 2012. From what I've seen these should be smaller changes yet.
If you do this you are off of the golden supported brick road. Since this server is production, and you don't have a good way to test this, I would find a 2008 server to develop with. I wouldn't want my name connected with the possible problems that could come up with a hack to move the rdl backwards.
Is there any chance of installing Reporting Services 2008 against an instance of SQL Server 2000? The docs clearly state that only SQL Server 2005 or 2008 are supported, but I thought I should ask anyway, for ways to bypass this limitation.
I should mention that I am not talking about the data source for my reports (which is a remote data source that can be any type of sql server). I am interested in the databases where the report server stores its things.
No, the reportserver and reportservertempdb REQUIRE 2005 or 2008. You could source data for your reports from a 2000 instance, but your reporting services databases need to be 2005 or 2008.
see: http://msdn.microsoft.com/en-us/library/ms157285.aspx and read the section on Database Server Version Requirements
I have no idea if this would work, however reporting services also depends on the SQL Server Agent service (for subscriptions) as well as the relational databases, so both would need to be compatible. If you have Reporting Services 2008 then you (or your organisation) must own a SQL Server 2008 license of some sort, therefore I cannot see why you would ever want to do this since you can install the SQL 2008 database engine to support your report server (on the same server, otherwise you would need an additional license).
Bear in mind that as of April 2008 SQL Server 2000 is no longer in mainstream support from Microsoft, so you should avoid implementing new infrastructure or functionality using this version wherever possible. The configuration you describe above, even if you got it to work, would be unsupported by Microsoft and probably all ISVs and partners.