I am trying to create a SSRS report with sql server 2005 BI. I have to use the existing data source to be consistent with the other reports, but in the SharedDataSources folder when I click add existing item, I cant find the Data source.
Can someone tell me where the Data Sources for SSRS reports store physically on a machine?
Thanks
It should be stored in the SSRS project. It will appear as .rds file.
Related
I am using Cognos 10. I have created a model in FM using some tables in DB2. Then I have created a package and published it. I have also generated reports on this in report studio. Everything went well and the report looks fine.
Now the actual problem is, I added some rows to the tables which I used for this project and the previous report is not updating. I tried refreshing data source in FM but it didn't update. So I had to create a new model and publish a package and generate a new report each time I add data to my DB2 tables.
I have seen Tableau reports being auto-update when database changes occurs. Is this possible with Cognos?
Is there any other way in which I can just do something in report studio and the report automatically updates to the new data present in DB2 tables?? So that I don't have to create a new model,package and report for each DB2 insert??
I met the same issue here if I use a Framework Manager model. The only solution that I found right now is to write SQL directly in Report Studio.
It can be problem with local cache. I had this issue before. The new data row was not shown in Report after insert. I needed to disable local cache in the Framework to make it work.
I want to create a report with .rdlc, in this case i want to join some table and put the result in table on the rdlc file. I got confused, coz there is no place to put my query in the report.
Did i have to write some coding to create the report, so i can use the query?
Regards
I suggest downloading SAP Crystal Reports (http://www.crystalreports.com/). If you are using SQL Server, use Business Intelligence to create the report through the server. The report viewer currently installed with Visual Studio is not user friendly.
(distinction, I'm talking about distributing a report--not deploying a report to a report server)
To our product we've recently added support for it so it can dump various stats to a database (mssql server). Since then, I've made reports (where the datasource is my own sql server). But if I want to get these reports into the hands of customers (pointing to their own database, obviously) so they don't need to make their own (or if they don't want/can't make their own) is there a good way to do this?
I'd rather not have to give instructions on how to use the report creator and have them copy/paste what I've done nor have them open it and change the datasource. I'm completely new to using SSRS and don't know any of its intricacies. I know I can query the database to see what reports are available, is there a way to just add an entire report to the database via code (c# or java)?
Assuming that they have SSRS installed and configured, and assuming that their DB (tables, SPs etc.) match your report - one of the way this could be done is:
When creating your report use a shared datasource (don't use one embedded into report)
Ask a customer to create shared data source in their SSRS instance under the same name, but pointing to their DB
Profit! That's it, all you have to to is to give them the RDL file, they will upload it to their SSRS. It will use shared datasource they provided to pull data from their DB
I am a newbie in Cognos. I am trying to create a report using report studio, I have the required package, and I want to create a report using a complex SQL query which has joins between three tables. Can anyone please give a suggestion to start building the report? Thanks!
How to write SQL for Cognos reports
FM is to create complex models. If you need a quick-and-dirty report you can specify custom SQL as the tutorial shows.
It would depend on how the data you see in Report Studio is modelled, typically a tool called Framework Manager is used connect to and model the source tables and views. Framework Manager creates the packages that you see in Report Studio, it can define relationships between entities like tables (if they're not already defined in the source database).
Not sure how to tell from Report Studio if the relationship has been defined properly other than trying to pull over fields from each table into the same Report Studio Query. It is best to talk to whoever designed the Framework Manager model or look at the model itself.
I have installed Crystal Reports and am using it in Visual Studio 2005.
Can anyone help me as to how i can use SQL Server 2000 to generate reports using Stored Procedures.
Im not sure i have understood the question. if you want SPs to write the RPT file for you then I cant answer.
What i have done for years is use Stored Procedures to do the heavy-lifting for the report. Simply create an sp with parameters. When you create your crystal report and adding data definitions in make sure that stored procedures are included. Then add parameters to the report which are inserted into the SP paramaters at runtime.
Using Views is also a good way to put all the data massaging work back onto the db server instead of the client. Send parameters from crystal to return a filtered dataset back to your report for printing.
Crystal Reports: Tutorials and Sample Code
http://msdn.microsoft.com/en-us/library/ms227881%28VS.80%29.aspx
Google search of "Crystal Reports Visual Studio Tutorial" returned that as the top result.
Start by creating a data source type of OLE DB, and choose your SQL Server Native Client. This option will be there for a new report, or if you set the data source; note that if you set a different data source for an existing report, your existing data fields may disappear from the report. Using integrated security is nice because you can control access to the data in the report in SQL Server.
Then in your database expert, click "Add Command", where you can call the shared procedure, add SQL, select your fields, etc.