Hello,
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnHello John,
Thank you for using Microsoft MSDN newsgroup!
I understand that you'd like to know if charts in report could be
compressed or use a vector format when exporting to PDF. If I'm off-base,
please let me know.
This behavior is a limitation of the product and we have received similar
request from another customer. However, currently there is no option to
compress charts or use a vector format for charts as you want for local
report.
The major difference for PDF rendering for the local report is that PDF
doesn't support compression of data while rendering. So it will take long
time when compared to the one from the server PDF rendering. But this
limitation is only for PDF and for other rendering extensions like Excel
etc don't have difference in behavior from the local and the server reports.
Verifying with our Development Team, I found that resolution is also not a
configurable setting for the PDF renderer. The documentation link which I
sent earlier
incorrectly lists DpiX and DpiY as available Device Information settings
for PDF.
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm
/rsp_prog_soapapi_dev_8bld.asp>
This documentation was corrected later for RS 2005 version:
<http://msdn2.microsoft.com/en-us/library/ms154682.aspx>
So unfortunately the DpiX and DpiY settings will have no effect when passed
to Render method.
Please rest assured your feedback on this is reported to the proper
channel. In the meantime, I also encourage you submit via the link below so
that product team could hear your sound directly:
http://lab.msdn.microsoft.com/productfeedback/default.aspx
You may want to consider using Excel rendering method but it may not meet
your requriment exactly. Or you may want to consider using a report server
to render the report for you other than using a local report.
If you have any questions or concerns on this, please feel free to let us
know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.sql
Showing posts with label size. Show all posts
Showing posts with label size. Show all posts
Friday, March 30, 2012
PDF Size with Chart
Hello,
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnI've noticed a similar strange behavior with PDF and charts with RS 2005.
I've had situations where the PDF download never ends :)
So for charts we have people export to TIFF.
It looks to be a bug with RS 2005.
"JPS" wrote:
> Hello,
> I am using ReportViewer in a web application. When there is a chart as part
> of a report and it is exported to PDF the file size is very large for a
> single page; typically 10-12 Mb.
> I am now supposed to manufacture a report that will be about 50 pages with a
> large graph on each page and I don't thing a 500Mb file size is acceptable.
> Isn't there a way for the charts to use a vector format instead or at least
> a compressed format?
> Thanks,
> John|||I have the same issue. We are creating a report with three charts, and it is
20 MB total file size. We are using local reports in an Asp .Net 2.0 page.
Any help would be greatly appreciated.
Thanks
Sam
"Carmine" wrote:
> I've noticed a similar strange behavior with PDF and charts with RS 2005.
> I've had situations where the PDF download never ends :)
> So for charts we have people export to TIFF.
> It looks to be a bug with RS 2005.
> "JPS" wrote:
> > Hello,
> >
> > I am using ReportViewer in a web application. When there is a chart as part
> > of a report and it is exported to PDF the file size is very large for a
> > single page; typically 10-12 Mb.
> >
> > I am now supposed to manufacture a report that will be about 50 pages with a
> > large graph on each page and I don't thing a 500Mb file size is acceptable.
> >
> > Isn't there a way for the charts to use a vector format instead or at least
> > a compressed format?
> >
> > Thanks,
> > John
I am using ReportViewer in a web application. When there is a chart as part
of a report and it is exported to PDF the file size is very large for a
single page; typically 10-12 Mb.
I am now supposed to manufacture a report that will be about 50 pages with a
large graph on each page and I don't thing a 500Mb file size is acceptable.
Isn't there a way for the charts to use a vector format instead or at least
a compressed format?
Thanks,
JohnI've noticed a similar strange behavior with PDF and charts with RS 2005.
I've had situations where the PDF download never ends :)
So for charts we have people export to TIFF.
It looks to be a bug with RS 2005.
"JPS" wrote:
> Hello,
> I am using ReportViewer in a web application. When there is a chart as part
> of a report and it is exported to PDF the file size is very large for a
> single page; typically 10-12 Mb.
> I am now supposed to manufacture a report that will be about 50 pages with a
> large graph on each page and I don't thing a 500Mb file size is acceptable.
> Isn't there a way for the charts to use a vector format instead or at least
> a compressed format?
> Thanks,
> John|||I have the same issue. We are creating a report with three charts, and it is
20 MB total file size. We are using local reports in an Asp .Net 2.0 page.
Any help would be greatly appreciated.
Thanks
Sam
"Carmine" wrote:
> I've noticed a similar strange behavior with PDF and charts with RS 2005.
> I've had situations where the PDF download never ends :)
> So for charts we have people export to TIFF.
> It looks to be a bug with RS 2005.
> "JPS" wrote:
> > Hello,
> >
> > I am using ReportViewer in a web application. When there is a chart as part
> > of a report and it is exported to PDF the file size is very large for a
> > single page; typically 10-12 Mb.
> >
> > I am now supposed to manufacture a report that will be about 50 pages with a
> > large graph on each page and I don't thing a 500Mb file size is acceptable.
> >
> > Isn't there a way for the charts to use a vector format instead or at least
> > a compressed format?
> >
> > Thanks,
> > John
Wednesday, March 28, 2012
pdf size due to images
We have a report with a number of external images. When the report is run
and exported to pdf, the resulting document is over 2mb (regardless of
whether the report is run in VS or the ReportManager). When the images are
changed from external to embedded, the resulting pdf document is around
500kb. This is great since the 2mb was causing issues with our client's
email server. When the modified rdl is imported to our client's system, the
resulting document is still around 500kb.
When the original rdl is modified on the client's system using
ReportDesigner - and all of the images are changed from external to embedded
- the resulting pdf document is still over 2mb!! I've verified any number
of times that the images are of type embedded.
Both systems are have reporting services at sp1. The only obvious
difference is that our environment is a developer edition of SQL Server and
the client's is Standard.
Is the difference in SQL the reason? Any other ideas/suggestions'
ThanksThis is NOT an issue between external vs. embedded images. During testing
the wrong image file was being used.
It DOES appear to be an issue with the way images are rendered to PDF.
Using other document types such as Word results in a smaller overall document
size.
Any suggestions/ideas for rendering to pdf are appreciated.
"PD" wrote:
> We have a report with a number of external images. When the report is run
> and exported to pdf, the resulting document is over 2mb (regardless of
> whether the report is run in VS or the ReportManager). When the images are
> changed from external to embedded, the resulting pdf document is around
> 500kb. This is great since the 2mb was causing issues with our client's
> email server. When the modified rdl is imported to our client's system, the
> resulting document is still around 500kb.
> When the original rdl is modified on the client's system using
> ReportDesigner - and all of the images are changed from external to embedded
> - the resulting pdf document is still over 2mb!! I've verified any number
> of times that the images are of type embedded.
> Both systems are have reporting services at sp1. The only obvious
> difference is that our environment is a developer edition of SQL Server and
> the client's is Standard.
> Is the difference in SQL the reason? Any other ideas/suggestions'
> Thanks|||The issue was resolved by: (1) upgrading to SP2 AND (2) reducing the size of
jpg images that are used in the report. ONLY upgrading to SP2 DID NOT solve
the problem - the original images were simply distorted/gray AND without a
reduction in overall pdf document size. The size of the images were reduced
using MS Photo Editor, although other editors seem to work also.
"PD" wrote:
> This is NOT an issue between external vs. embedded images. During testing
> the wrong image file was being used.
> It DOES appear to be an issue with the way images are rendered to PDF.
> Using other document types such as Word results in a smaller overall document
> size.
> Any suggestions/ideas for rendering to pdf are appreciated.
>
> "PD" wrote:
> > We have a report with a number of external images. When the report is run
> > and exported to pdf, the resulting document is over 2mb (regardless of
> > whether the report is run in VS or the ReportManager). When the images are
> > changed from external to embedded, the resulting pdf document is around
> > 500kb. This is great since the 2mb was causing issues with our client's
> > email server. When the modified rdl is imported to our client's system, the
> > resulting document is still around 500kb.
> >
> > When the original rdl is modified on the client's system using
> > ReportDesigner - and all of the images are changed from external to embedded
> > - the resulting pdf document is still over 2mb!! I've verified any number
> > of times that the images are of type embedded.
> >
> > Both systems are have reporting services at sp1. The only obvious
> > difference is that our environment is a developer edition of SQL Server and
> > the client's is Standard.
> >
> > Is the difference in SQL the reason? Any other ideas/suggestions'
> > Thanks
and exported to pdf, the resulting document is over 2mb (regardless of
whether the report is run in VS or the ReportManager). When the images are
changed from external to embedded, the resulting pdf document is around
500kb. This is great since the 2mb was causing issues with our client's
email server. When the modified rdl is imported to our client's system, the
resulting document is still around 500kb.
When the original rdl is modified on the client's system using
ReportDesigner - and all of the images are changed from external to embedded
- the resulting pdf document is still over 2mb!! I've verified any number
of times that the images are of type embedded.
Both systems are have reporting services at sp1. The only obvious
difference is that our environment is a developer edition of SQL Server and
the client's is Standard.
Is the difference in SQL the reason? Any other ideas/suggestions'
ThanksThis is NOT an issue between external vs. embedded images. During testing
the wrong image file was being used.
It DOES appear to be an issue with the way images are rendered to PDF.
Using other document types such as Word results in a smaller overall document
size.
Any suggestions/ideas for rendering to pdf are appreciated.
"PD" wrote:
> We have a report with a number of external images. When the report is run
> and exported to pdf, the resulting document is over 2mb (regardless of
> whether the report is run in VS or the ReportManager). When the images are
> changed from external to embedded, the resulting pdf document is around
> 500kb. This is great since the 2mb was causing issues with our client's
> email server. When the modified rdl is imported to our client's system, the
> resulting document is still around 500kb.
> When the original rdl is modified on the client's system using
> ReportDesigner - and all of the images are changed from external to embedded
> - the resulting pdf document is still over 2mb!! I've verified any number
> of times that the images are of type embedded.
> Both systems are have reporting services at sp1. The only obvious
> difference is that our environment is a developer edition of SQL Server and
> the client's is Standard.
> Is the difference in SQL the reason? Any other ideas/suggestions'
> Thanks|||The issue was resolved by: (1) upgrading to SP2 AND (2) reducing the size of
jpg images that are used in the report. ONLY upgrading to SP2 DID NOT solve
the problem - the original images were simply distorted/gray AND without a
reduction in overall pdf document size. The size of the images were reduced
using MS Photo Editor, although other editors seem to work also.
"PD" wrote:
> This is NOT an issue between external vs. embedded images. During testing
> the wrong image file was being used.
> It DOES appear to be an issue with the way images are rendered to PDF.
> Using other document types such as Word results in a smaller overall document
> size.
> Any suggestions/ideas for rendering to pdf are appreciated.
>
> "PD" wrote:
> > We have a report with a number of external images. When the report is run
> > and exported to pdf, the resulting document is over 2mb (regardless of
> > whether the report is run in VS or the ReportManager). When the images are
> > changed from external to embedded, the resulting pdf document is around
> > 500kb. This is great since the 2mb was causing issues with our client's
> > email server. When the modified rdl is imported to our client's system, the
> > resulting document is still around 500kb.
> >
> > When the original rdl is modified on the client's system using
> > ReportDesigner - and all of the images are changed from external to embedded
> > - the resulting pdf document is still over 2mb!! I've verified any number
> > of times that the images are of type embedded.
> >
> > Both systems are have reporting services at sp1. The only obvious
> > difference is that our environment is a developer edition of SQL Server and
> > the client's is Standard.
> >
> > Is the difference in SQL the reason? Any other ideas/suggestions'
> > Thanks
PDF Rendering
OK still having the problem of a blank page after every report. I have reset
all my page sizes, margins etc. Ensured that my page size is minus my
margins etc. And still this is happening. Any insight would be lovely
thanks. Cannot deploy reports to customers application until this is sorted.Do you have a page break after any groups?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nat Johnson" <NatJohnson@.discussions.microsoft.com> wrote in message
news:60472AC6-90D7-4B80-84EA-C78ACFE98022@.microsoft.com...
> OK still having the problem of a blank page after every report. I have
> reset
> all my page sizes, margins etc. Ensured that my page size is minus my
> margins etc. And still this is happening. Any insight would be lovely
> thanks. Cannot deploy reports to customers application until this is
> sorted.|||No page break Brain. Managed to get it sorted yesterday afternoon with much
playing around with margins etc. Even are setting the page size to the
normal width less the margins didn't seem to help. I had to bring it in a
lot further.
"Brian Welcker [MSFT]" wrote:
> Do you have a page break after any groups?
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Nat Johnson" <NatJohnson@.discussions.microsoft.com> wrote in message
> news:60472AC6-90D7-4B80-84EA-C78ACFE98022@.microsoft.com...
> > OK still having the problem of a blank page after every report. I have
> > reset
> > all my page sizes, margins etc. Ensured that my page size is minus my
> > margins etc. And still this is happening. Any insight would be lovely
> > thanks. Cannot deploy reports to customers application until this is
> > sorted.
>
>|||What about the <Body> properties width and height. Do they conform to your
paper dimensions. And even if they do, is the 'can grow' option on in your
fields? Sometimes this can push your report past your defined margins and
create an extra page.
--
Message posted via http://www.sqlmonster.com|||I've had this problem a few times...make sure that your report width is small
enough to fit on one page. Try to keep it under 22.75cm wide. The extra page
is just the edges wrapping around to the next page.
"Nat Johnson" wrote:
> OK still having the problem of a blank page after every report. I have reset
> all my page sizes, margins etc. Ensured that my page size is minus my
> margins etc. And still this is happening. Any insight would be lovely
> thanks. Cannot deploy reports to customers application until this is sorted.
all my page sizes, margins etc. Ensured that my page size is minus my
margins etc. And still this is happening. Any insight would be lovely
thanks. Cannot deploy reports to customers application until this is sorted.Do you have a page break after any groups?
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nat Johnson" <NatJohnson@.discussions.microsoft.com> wrote in message
news:60472AC6-90D7-4B80-84EA-C78ACFE98022@.microsoft.com...
> OK still having the problem of a blank page after every report. I have
> reset
> all my page sizes, margins etc. Ensured that my page size is minus my
> margins etc. And still this is happening. Any insight would be lovely
> thanks. Cannot deploy reports to customers application until this is
> sorted.|||No page break Brain. Managed to get it sorted yesterday afternoon with much
playing around with margins etc. Even are setting the page size to the
normal width less the margins didn't seem to help. I had to bring it in a
lot further.
"Brian Welcker [MSFT]" wrote:
> Do you have a page break after any groups?
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Nat Johnson" <NatJohnson@.discussions.microsoft.com> wrote in message
> news:60472AC6-90D7-4B80-84EA-C78ACFE98022@.microsoft.com...
> > OK still having the problem of a blank page after every report. I have
> > reset
> > all my page sizes, margins etc. Ensured that my page size is minus my
> > margins etc. And still this is happening. Any insight would be lovely
> > thanks. Cannot deploy reports to customers application until this is
> > sorted.
>
>|||What about the <Body> properties width and height. Do they conform to your
paper dimensions. And even if they do, is the 'can grow' option on in your
fields? Sometimes this can push your report past your defined margins and
create an extra page.
--
Message posted via http://www.sqlmonster.com|||I've had this problem a few times...make sure that your report width is small
enough to fit on one page. Try to keep it under 22.75cm wide. The extra page
is just the edges wrapping around to the next page.
"Nat Johnson" wrote:
> OK still having the problem of a blank page after every report. I have reset
> all my page sizes, margins etc. Ensured that my page size is minus my
> margins etc. And still this is happening. Any insight would be lovely
> thanks. Cannot deploy reports to customers application until this is sorted.
Monday, March 26, 2012
PDF Fit to Page
I have reports being accessed through report manager in the UK and USA.
The reports were created to fit on an A4 page size which works fine in
UK but because the standard paper size in USA is Letter the export to
PDF is producing reports that are rendering to multiple pages.
Is there anyway I can set the PDF to fit to page either in the report
itself or in report manager?
If this isn't possible can I create a custom renderer that inherits the
standard PDF renderer but allows me to set the fit to page?In the report you will need to set the correct size, in the layout tab, in
report proeperties, to pen this dialog, just right click(or left depends ond
you configuration), and select properties, then move to the layout tab, and
set the correct paper size, adjust the margins as you need it, do the same
with the report's body, but you have to be carefull,
the body width must be less or equal than the
Page Width(the one in layou) - the sum of the margins if you do not meet
this requirements, you'll have pagebreaks in pdfs.
You can find more information for this at the following link:
http://blogs.msdn.com/chrisbal/
--
Eduardo Fonseca
"Nathan" wrote:
> I have reports being accessed through report manager in the UK and USA.
> The reports were created to fit on an A4 page size which works fine in
> UK but because the standard paper size in USA is Letter the export to
> PDF is producing reports that are rendering to multiple pages.
> Is there anyway I can set the PDF to fit to page either in the report
> itself or in report manager?
> If this isn't possible can I create a custom renderer that inherits the
> standard PDF renderer but allows me to set the fit to page?
>
The reports were created to fit on an A4 page size which works fine in
UK but because the standard paper size in USA is Letter the export to
PDF is producing reports that are rendering to multiple pages.
Is there anyway I can set the PDF to fit to page either in the report
itself or in report manager?
If this isn't possible can I create a custom renderer that inherits the
standard PDF renderer but allows me to set the fit to page?In the report you will need to set the correct size, in the layout tab, in
report proeperties, to pen this dialog, just right click(or left depends ond
you configuration), and select properties, then move to the layout tab, and
set the correct paper size, adjust the margins as you need it, do the same
with the report's body, but you have to be carefull,
the body width must be less or equal than the
Page Width(the one in layou) - the sum of the margins if you do not meet
this requirements, you'll have pagebreaks in pdfs.
You can find more information for this at the following link:
http://blogs.msdn.com/chrisbal/
--
Eduardo Fonseca
"Nathan" wrote:
> I have reports being accessed through report manager in the UK and USA.
> The reports were created to fit on an A4 page size which works fine in
> UK but because the standard paper size in USA is Letter the export to
> PDF is producing reports that are rendering to multiple pages.
> Is there anyway I can set the PDF to fit to page either in the report
> itself or in report manager?
> If this isn't possible can I create a custom renderer that inherits the
> standard PDF renderer but allows me to set the fit to page?
>
PDF files with images get unexpectedly large in SQL Server 2000 Reporting Services
When using quite small JPEGS (~ 800 KB) in a report the exported PDF is a few megabytes of size. Am I missing something (e.g. some kind of compression)?
Can anyone give me a hint on this one?
Thanks,
Neno
There is a known bug in 2000 (which I know wasn't fixed in the SP2 beta -- don't know about SP2 RTM, though) in the PDF renderer -- It causes images of any type to be converted to bitmaps, then rendered. I bet this is what you're running into.
|||i want to download some programme so i need urgent thanks
|||
I would suggest installing RS SP2 and the latest QFE available (KB912424).
Thank you,
Nico
|||This problem still occurs in SQL Reporting 2005 localreports. An issue has been opened for this problem. Please add your vote. https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=232211PDF files with images get unexpectedly large in SQL Server 2000 Reporting Services
When using quite small JPEGS (~ 800 KB) in a report the exported PDF is a few megabytes of size. Am I missing something (e.g. some kind of compression)?
Can anyone give me a hint on this one?
Thanks,
Neno
There is a known bug in 2000 (which I know wasn't fixed in the SP2 beta -- don't know about SP2 RTM, though) in the PDF renderer -- It causes images of any type to be converted to bitmaps, then rendered. I bet this is what you're running into.
|||i want to download some programme so i need urgent thanks
|||
I would suggest installing RS SP2 and the latest QFE available (KB912424).
Thank you,
Nico
|||This problem still occurs in SQL Reporting 2005 localreports. An issue has been opened for this problem. Please add your vote. https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=232211sqlPDF files with images get unexpectedly large in SQL Server 2000 Reporting Services
When using quite small JPEGS (~ 800 KB) in a report the exported PDF is a few megabytes of size. Am I missing something (e.g. some kind of compression)?
Can anyone give me a hint on this one?
Thanks,
Neno
There is a known bug in 2000 (which I know wasn't fixed in the SP2 beta -- don't know about SP2 RTM, though) in the PDF renderer -- It causes images of any type to be converted to bitmaps, then rendered. I bet this is what you're running into.
|||i want to download some programme so i need urgent thanks
|||
I would suggest installing RS SP2 and the latest QFE available (KB912424).
Thank you,
Nico
|||This problem still occurs in SQL Reporting 2005 localreports. An issue has been opened for this problem. Please add your vote. https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=232211
Subscribe to:
Posts (Atom)