Wednesday, March 28, 2012

Print button generates hugh spooled print files

Hi!
We are currently using a different third party tool to print out pdf-files
generated from SQL Server 2000 Reporting Services. We are a fairly large
international cooperation and have a centralized citrix it environment with
different band width to different places in the world. This makes the print
file size critical.
Because there havenâ't been any really good ways to print out reports before
sp2 we have hoped a lot of the sp2 print functionality. Now itâ's installed in
our test enviromnet and we are pretty disappointed.
It seems like the reports are converted to tiff-format and then printed and
the print file size is huge. We tested to print out a report with six pages
(A4-format) with different techniques and this is the result when it comes to
spooled print file sizes:
1. Using RS print button (14.1 MB)
2. Exporting to TIFF-format from RS and than print (14 MB)
3. Exporting to PDF-format and print with gsprint (ghostscript) using a
windows generic print driver (1.43 MB)
4. Exporting to PDF-format and print with gsprint (ghostscript) using a
print driver specialized for the current printer, hp laserjet (852 KB)
5. Exporting to PDF-format and print with acrobat reader (531 KB)
I have a couple of questions regarding this:
1. Is this right? Is the report converted to TIFF-format when pressing the
print button and is it right that the spooled print file should be this large
and in that case why is it done in this way?
2. Is there any work around for this? Is there any way to get a smaller file?
3. Is this the way it will be implemented in SQL Server 2005 as well?
Regards,
/MattiasHi Mattias,
I also noticed the problem and posted a while back but not got a reply yet
(we too also use Citrix and need to address the bandwidth issue!).
--
Ben
"MattiasT" wrote:
> Hi!
> We are currently using a different third party tool to print out pdf-files
> generated from SQL Server 2000 Reporting Services. We are a fairly large
> international cooperation and have a centralized citrix it environment with
> different band width to different places in the world. This makes the print
> file size critical.
> Because there havenâ't been any really good ways to print out reports before
> sp2 we have hoped a lot of the sp2 print functionality. Now itâ's installed in
> our test enviromnet and we are pretty disappointed.
> It seems like the reports are converted to tiff-format and then printed and
> the print file size is huge. We tested to print out a report with six pages
> (A4-format) with different techniques and this is the result when it comes to
> spooled print file sizes:
> 1. Using RS print button (14.1 MB)
> 2. Exporting to TIFF-format from RS and than print (14 MB)
> 3. Exporting to PDF-format and print with gsprint (ghostscript) using a
> windows generic print driver (1.43 MB)
> 4. Exporting to PDF-format and print with gsprint (ghostscript) using a
> print driver specialized for the current printer, hp laserjet (852 KB)
> 5. Exporting to PDF-format and print with acrobat reader (531 KB)
> I have a couple of questions regarding this:
> 1. Is this right? Is the report converted to TIFF-format when pressing the
> print button and is it right that the spooled print file should be this large
> and in that case why is it done in this way?
> 2. Is there any work around for this? Is there any way to get a smaller file?
> 3. Is this the way it will be implemented in SQL Server 2005 as well?
> Regards,
> /Mattias

No comments:

Post a Comment