Are there some way to add a cooments in my report when I ask for a parameters, before user execute it?
I'm ready adding a comment in a SQL Server Reporting Services, security option, and the user can read it when they pass the mouse on the option. But in this way I thinking that I will lost this in the next deploy, that is true?
The comments added to reports won't be lost when you deploy the report again over this: When deploying reports from BIDS, some information is kept on the server. It's not a "Delete" then "load." The information kept is the security settings, the comments, some parameter information, such as default parameters and subscriptions.
Other than these comments stored in SSRS, there is not a way to add comments to the report before the display of the parameters. If you really need to do something like this, then you should build an interface to gather the parameters yourself and then display or redirect to the reports.
Related
I am interested in learning how to optimize my Action Property of an object in my SSRS Report.
All of the linked reports use the same Data Source. So, should I put the Data Source in the Shared folder and have all the report projects in the same solution?
The Action properties for the object have the options under "Enable as an action":
Go to report
Go to bookmark
Go to URL
The option for "Go to URL" works for the main report that is sent as an email alert subscription, but, as for the other reports that launch in a browser, I wonder if the option "go to report" will be a better choice? Would it be, and how would that be set?
Well, this answers part of my question:
The Go to report action is mostly used to go to a subreport, where you hand over a parameter or a value. If you dont pass any of these Go to URL would be the better choice.
How you handle your datasets depends on your setup. If your reports load fast and the datasets also, dont bother with shared datasets. Just load the same dataset again.
You can also insert a sever between your database and the report server which caches all the datasets. So you just load your dataset once in the morning and the reports use the cached one.
Our IT Dept gave me an SSRS 2016 Dev Instance to play with. But I have two things that I need to figure out, as I've hit a dead end on:
The AppId I need to run our subscriptions under. It's needed to be setup on the SSRS Server to allow Local Login or the reports would not work.
Can some explain why we would need to allow login locally? Or even if it's the correct way to handle it, or should I be setting up something different for the AppId to work correctly?
I also need to be able to setup shared schedules. However when I click the settings gear, I only have 'My Subscriptions', and I understand I need 'Site Settings' to show up here.
What permissions do they need to setup in order for me to gain access to Site Settings?
Sorry, I'm not sure how to answer the first one. I think because SSRS is an additional service external of SQL Server it needs a local SQL Server login. Not really my forte.
By default there is a BUILTIN\Administrators role. The following link will describe who gets placed in the BUILTIN\Administrators role. Once you're in there, you can get to site settings and add your own security settings and shared schedules.
BUILTIN\Administrators info link
Hope this helps.
I'm a very new user to SSRS. I learned the basic things and am able to make reports using VS 2008 and BIDS. But I can't move further. I want to use the dynamic data source. My issues are:
First the user should input four credentials: a)Server name b) database name c) user id 4) password. It will help to make the connection with database and make the data source. The credential should be stored in session or cookie.
Now the user will be able to see all the reports without giving the credential because he/she has already given them.
I made a dynamic data source but the credentials are asked for every time I open a report.
Any demo project or an articles will be highly appreciated.
It sounds like SSRS alone will not accomplish what you want. SSRS will not provide a good interface for end users to create new datasources, or change existing datasources. There are some potential workarounds that get some of the functionality you desire, such as a method to change servers found at:
http://blog.softartisans.com/2011/04/19/how-to-create-a-dynamic-reporting-services-shared-data-source-using-linked-servers/
(requires the ability to use linked servers.)
But to manage the user session or cookies, you will need more than SSRS. The easiest way to get at this will be with a .NET web site to manage the credentials. It might be able to use a ReportViewer control, or other method of accessing SSRS, such as URL access, to get reporting functionality.
I've build an asp.net site with a report viewer control that displays reports hosted on our reporting services report server. Everything works great. But now I need to do the same thing with a public facing site, where I'll need to access my report server through the firewall.
My question is: How do I lock this down to make sure that the end user can only access certain reports?
I think that all I need to do is make sure my IIS, in my DMZ, can talk to the report server. But, I think I'll need to impersonate a user that only has access to the reports I want to make available. On the other hand, if my report server is only accessible from the DMZ, then I won't need to worry about the end user directly connecting to the report server. I seems like any report I want to serve to the outside world just needs to be accessible by the default ASPNET account? I hoping someone can confirm my speculation or tell me where I'm wrong.
I had this problem too. What I had to do was make sure that each report takes a parameter from the application. If your authenticated users have an role through a role provider, and public users do not, you could pass the role as a parameter to the report through the application. That way if a user is not authenticated, the parameter will be null, and the report will not execute.
I've been working with SSRS 2005 reports for a little while now, and I've had a few requests come across asking for individual users to be able to save the parameters they use for the next time they run the report. Is this feasible? Is it a part of the "My Reports" role? Any thoughts?
I don't know if that can be done using the report manager, but you could always use URL parameters and pass through that way, then just give them the link to follow which will take them to their report (or render it as a PDF or other format if you wish) and already have the parameters passed in.
Here is a link that will take you to a lot of MSDN documentation about URL Access for your Reports.
I think you'll have to stop using the built-in UI and build your own report front-end to do that. I have always used RS this way and it is not all that complicated.