I am developing a WPF application in VB. Net and I'm using SQL Server Reporting to create my reports.
I have a report that contains the specifications for a machine and I would add the PDF file that contains additional information to report and then print it.
Is it possible to dynamically add PDF files in a RDLC report?
Or is there a way to solve this problem
Thank you
i dont think that reports server has any inbuilt support for pdf's. You might be able to buy one, but i think i would save the pdf's as jpegs and just put those in the report instead
Related
We are using the IBM Cognos Report Studio for Making the Reports.
And we have 1000s of reports developed and using.
Now i need to fetch all the SQL queries written in these 1000+ reports.
For that at present i am opening the report studio for each individual report and getting the query.
But it is very tedious job and taking months to get all the SQLs in these 1000+ reports.
So i am looking for a way to get all these queries from database behind Cognos studio.
Does these report parameters (including the SQL) store in a Database or only in Contentstore?
If it store in DB then is it possible to access the Report Studio in a Database tool like Oracle SQL Developer?
So that i can fetch all the SQLs in one shot from the database table.
Thanks for the help!
My experience migrating from one reporting product to another is like what you are asking. I think I had 7000 reports that I was aware of plus many reports sitting on workstation hard drives. At some point along the way we realized that the new product had different features than the old one, so report redesign was a good option in most cases. It took 18 months once we actually started working on the reports. That was to replace the 700 "standard" reports. Users were on their own (with support from IT and subject matter experts) for their custom work. I now have about 19,000 reports in Cognos.
Except where the report developer wrote SQL in a SQL object in the Queries area, Cognos reports do not contain SQL code. Cognos generates the SQL at runtime based on the report spec and user interaction (what parameters they set, what page the opened, etc.). Short of writing your own report spec parser, duplicating the work that Cognos does for you, there is no way I know of to generate the SQL.
One possibility: I haven't dug too deeply into the Cognos SDK. There may be a method there to generate the SQL for each report. Then you can do it automatically. Be aware that for thousands of reports you'll want to run this process during non-work hours. It could run for hours and may use a lot of resources.
Another possibility: Turn on native query logging (Cognos Administration | System | All dispatchers | | Set properties | Settings | Logging | Check the boxes for "Audit the native query..."). Then have a person, a product like those from Motio, or a Cognos SDK program you create yourself run every report. Then you can get the SQL from the Audit database. Of course, the problem here is answering prompts. It will probably take a person to run these.
To add two columns to a list, or two data elements to a report or page header or footer, or two filters (I don't know what you mean by "clause"), you'll want to use the Cognos SDK.
Choose relevant examples of different types of reports.
Examine the XML report spec for each of those reports.
Determine how to identify where the new element should appear in the XML.
Write a program (probably in C# or Java) to use the SDK to...
inspect every report in your environment.
determine which pattern the report fits.
add the data elements.
save the report.
I want to generate a csv report with the following format in SSIS -
Some Static Text - 1
Data from SQL
Some Static Text - 2
Data From SQL
I was thinking to create a report with these static texts in my report and generate the SQL data at runtime. But i can not fix the position of the Some Static text - 2 as the records from SQL can be 'n' in numbers.
I am newbie to SSIS, any help is much appreciated
You need SSRS. You can build reports for it in Visual Studio. SSIS is an ETL tool (Extract, transform, load) which is primarily used to aggregate data, migrate data, consolidate data, etc. SSRS is a tool that allows end-users to consume dynamic reports that you provide.
EDIT:
Install SSRS and configure it so that it's working:
https://msdn.microsoft.com/en-us/library/ms143711.aspx
I assume you already have SSDT since you mentioned SSIS, but just in case you don't:
https://msdn.microsoft.com/en-us/hh500335(v=vs.103).aspx
Then you'll open Visual Studio, create a new SSRS project, make a new report, define your datasource(s), and use the toolbox to add tables or whatever other display you need. It can also use parameters if you need user-input. Static content can be placed wherever you need it - and different datasets can be displayed wherever you need them, as well.
I would like to help more, but it sounds like you are starting from scratch and I can't possibly tell you everything there is to know about SSRS in this forum. So, here is an SSRS Tutorial:
https://msdn.microsoft.com/en-us/library/ms167305.aspx
Good luck - SSRS/SSIS/SSDT are awesome tools so I'm sure you'll find what you need.
What I got:
An SQL Server database with x amount of tables
An empty Word 2010 document
What I would like to achieve:
To fill the empty Word document with data from a specific table in my database.
What I've tried so far:
Microsoft Office guide to import data using the Data Connection Wizard (found here)
This didn't work out very well for me and I'm not very sure why.
Question
Am I approaching this in the right manner with the Data Connection Wizard, or am I missing out on something less complicated and more suiting of my needs?
There are many options. Assuming that you want to use the data writing a document and do it more often than once (so automated) you can execute one of the following:
"For the knowledgeable": create a SQL script that spits out RTF (or maybe even XML for docx) and open the RTF in Word. The SQL script can of course be encapsulated in a web page or exe. Note that is can be quite hard to get tables right. Try to stick to TAB-s.
"From within Word": we use ourselves our own product Invantive Composition (free version available for download). You enter the view or table names as blocks in the template designer (modeller ribbon) and press Publish in the end user ribbon.
"The BI way": use a program such as iReports or Crystal Reports or Access, and write a report that you save as RTF, doc or docx.
You could try SQL Workbench. I've always had great success with it, they also feature exports as CSV if I'm not mistaken. Read more here.
we currently use SQL Server Reporting Services to create reports based on SQL data. We are at the moment able to include images coming from a varbinary(Max) column of a SQL database table. Now in those table several other formats are stored including PDF and MS Word and Excel documents. We would like to render a report including those documents at the end but we could not find any suggestions, especially for doc and xls format.
Is that possible? And if yes, how?
Thanks for your help :)
Tom
I faced the same requirement in my project and the solution I see is preprocess those embedded documents, converting them to an images (per page in embedded documents). And then SSRS report itself will simply use image rendering control to embed those documents.
It looks like iText can meet all your requirments http://itextpdf.com/
I have a database to which I upload files (such as PDFs, images, etc). I save these to the database as Varbinary (max).
I upload these files using C# MVC. What I was wondering is how can I view these files using a T-SQL query, not .net.
Is this possible?
Not directly.
Why don't you write a simple viewer application?
There are free and commercial ones out there. I haven't used this one, but it does have a trial version: SQL Image Viewer
No, you need to extract the files in order to view them.
SQL Server and SSMS (SQL Server Management Studio) don't have a facility to view binary data in this way.
You can use the sp_OAxxxx functions (the COM interaction functions) to create the appropriate viewers, but ultimately these viewer will require the data written to disk.