The above is the Excel version that I've exported using SSRS, and have a look at below version, using same exact data, export to PDF:
Noticed there are certain records having a different milliseconds issues. Anyone have any idea how to fix it? PDF version is correct which align with the record from DB
I've found out the problem. Take second row for example, the data stored in DB is 14:02:16.899, when we export this data to excel, excel will automatically round it up while PDF will round down and hence the reason for the problem.
The solution I came up with was, on my query, format the transactiondatetime to have a consistent value instead of letting Excel and PDF rounding using their own mechanism.
Any other solutions or suggestions are welcome too
Related
I have a report in SSRS which I have build using report builder. So the thing is I want to have a pivot on the data and it works fine in the preview also when I export the rendered report into Excel. The issue comes up when I export the report into CSV. I have attached 4 images which will help in understanding my issue.
I am using a matrix to build the report which works fine when I export it into Excel.
This is the output of the report when exported into excel.
This is the output of the report when exported into csv
Can someone please help me with this?
Thanks
Unfortunately, that is how the CSV export works. It is not pretty.
More often than not, when it comes to reports that are more than just simple tables of data, the CSV data is almost useless after export.
Your best bet would be to create a report that is a little more friendly toward CSV exports, or avoid exporting to CSV if you don't have to. Excel tends to work much better for most exports.
I have an access dataset that has multiple queries. I update my linked excel tables and then export the queries again so I have access to the analysis I set up easily with updated data. The problem I am having is that sometimes when I export the query to excel it gives me a prompt warning me that it is going to overwrite the old file. I tell it to proceed and it runs through the export process but when I check the export file it is still the old file and not even the date modified column in windows explorer has changed. Some days certain queries have this problem and other days they all work. I do not have any clue why. I can delete the original file and run the export and it will work fine but this is a daily activity if not multiple times a day for multiple queries, manually deleting adds quite a bit of work and if I forget to delete it will possibly not export and then I am working with the wrong data. Is there anyway to fix this issue without getting into VBA which I have a very limited knowledge of.
We have some SSRS 2005 reports, hosted on a report server. When we try to export the reports to excel its taking more than usual time to download. The reports otherwise takes acceptably reasonable time to render.
When i ran SQL profiler against the report server found that, it internally is calling "ReadChunkPortion" sp thousands of times. I am assuming this has something to do with the pagination.
Can we conditionally disable pagination, while doing an export ? Appreciate any help/directions.
You may have luck changing the InteractiveHeight property to 0, as described in the last sentence on this page. This may affect the way the HTML renders, though, so be aware of the impact it might have.
In my experience, SSRS exports to Excel are generally inefficient, and the bigger the dataset the more frustrating it gets. It seems like there is little you can do to change this.
If setting the InteractiveHeight property doesn't work, and you really need the Excel export to run faster, you may just have to export to a .csv then open in Excel. Unfortunately, it requires more steps from the user, but depending on the size of your report, it could still be faster than sitting and waiting for the Excel export to complete.
We have been provided a form, layed out in Excel, that needs to be filled in based on data we have sitting in our SQL database.
I'm trying to determine the best way to electronically fill the form in. I could create an SSRS report, and lay it out as close as possible to the form provided, but I was wondering if I could use the excel file as a template in SSIS and have SSIS fill in the various fields.
It is not a simple table spreadsheet.
Use an SSIS package, connect to your DB and do the transformations on the package itself, there are several components, I'm pretty sure you will be able to deal with all the situations.
You could use the report and save it as excel but I think will be more complicated.
One thing to consider is that SSRS has limitations when exporting to excel. There is a limit of 60k rows. If you try to export more you will get:
Excel Rendering Extension: Number of rows exceeds the maximum possible rows per sheet in this format; Rows Requested: 209048, Max Rows: 65536
There is a work around to this but its time consuming.
This is an excel 2003 limitation and SSRS 2008 cannot export to excel 2007
I have an Oracle query and I want to export the query results to an excel file daily. I've looked into both SSRS and SSIS and am not sure which would be better to use.
The query is a normal select that returns 10-20 fields. It is pretty straight forward with a couple joins and where clauses. It selects DISTINCT to get rid of duplicate rows.
It's a straight mapping from the query to the excel file.
Does SSIS have performance advantages over SSRS?
I was leaning toward SSRS because it's very simple to set up and there are added benefits of being able to easily run our extract/report with different dates through the SSRS web UI.
SSIS seems like it will be more complex to set up, but still simple. However, it seems I would have to handle how to rename the extracts without using the main excel "template" so there are more steps involved. Also having issues getting parameters to work with Oracle queries.
Even though I am a big fan of SSIS, I would go with SSRS in this scenario.
Your requirement is that you simply need data in an Excel file. Though both SSIS and SSRS can do this task. SSRS has slight advantage in what you are trying to achieve.
You can format the Excel file in SSRS report however you would like to.
Similar to SSIS package that is easy to configure, SSRS also has easier development process. You can design and populate however you would like.
SSIS requires a SQL job to schedule it in order to run the package and then send you the Excel file or save it to some location. However in SSRS, you can simply create a subscription and export the Excel file to particular folder or send it to you in an email.
If you ever want to change the file export format, SSRS already does that for you.
Some of the points that I could think of.
This isn't a report, so don't use Reporting Services.
The SSIS package necessary for this is a single Data Flow task with two components: an "OLE DB Source" for your Oracle query, and an "Excel Destination". Draw a connection between the two components, configure them, press F5 and you're done.
Almost any property in SSIS can be set to the value of an expression. This includes the "ExcelFilePath" property of the Excel Connection Manager. Simply set that to an expression that appends the date to the file path, and you'll be set as long as you only run the package daily.
If you need to run it more than once a day, then simply precede the Data Flow task with a File System task to delete any previous version of the file.
Just tried this quickly myself and found one small issue. The data source I used included VARCHAR columns. The Excel Destination wanted Unicode, so I had to place a Data Conversion component between source and destination.
This link has a nice evaluation of the case you are presenting:
http://theruntime.com/blogs/gscarfone/archive/2009/07/15/data-dump-to-excel-through-ssis-and-ssrs.aspx
Basically it depends on your particular scenerio.
Hope it helps...