Print File Size

Just installed SP2 and started experimenting with the print functionality.
The size of the print jobs are huge. I had a fairly simple six page report
with a spooling size of over 100 mb, a single page over 17mb. Is there
anything that can be done to reduce this size . If not, we will not be able
to use the functionality as the network just will bog down - it is back to
printing out pdf files - which the users do not like.
Any hope of getting around this?This is the current behavior and there is no workaround. We are looking at
what we can do to make this better for the Yukon Release.
--
| Thread-Topic: Print File Size
| thread-index: AcVi/0NJpHDoEkgjQrGWFSnnPT784w==| X-WBNR-Posting-Host: 24.97.250.114
| From: "=?Utf-8?B?Y2hyaXM=?=" <chris@.discussions.microsoft.com>
| Subject: Print File Size
| Date: Fri, 27 May 2005 14:01:33 -0700
| Lines: 12
| Message-ID: <BBD25630-CC0A-4176-AEE4-03EC7BE22C6D@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:44927
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Just installed SP2 and started experimenting with the print
functionality.
| The size of the print jobs are huge. I had a fairly simple six page
report
| with a spooling size of over 100 mb, a single page over 17mb. Is there
| anything that can be done to reduce this size . If not, we will not be
able
| to use the functionality as the network just will bog down - it is back
to
| printing out pdf files - which the users do not like.
|
| Any hope of getting around this?
|
|
|
|
|

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

Primary Key Help

Hi am fairly new to VS and very new to Access. I am managing somewhat. I have access to the database, I get inside my tables and I can change what needs to be changed. However I want to know how to work with primary keys. As of right now I am using 4 tables in my app. If i run my program all of the tables get filled in just fine. However if I run it again, none of the tables get updated because I have a primary key on a few of the tables columns.

Dim ADOConn As ADODB.Connection

Dim recSet As ADODB.Recordset

ADOConn = New ADODB.Connection

recSet = New ADODB.Recordset

ADOConn.Provider = "Microsoft.Jet.OLEDB.4.0"

ADOConn.ConnectionString = "C:\Documents and Settings\christopher.cornell\Desktop\MyDB.mdb"

ADOConn.Open()

recSet.Open("select * from Table1", ADOConn, ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)

recSet.AddNew("Column1", textbox1.text) 'Primary key on this. When i try to add the same thing over

'no other tables will get updated.

recSet.Update()

recSet.Close()

The first time through will be just fine, however if I run it again it wont update the rest of my tables. It seems to run everything (stepping through the debugger) but it is not reflected in the tables. I hope what I am trying to do makes sense.

Hi Chris,

The issue here is that a primary key is what is referred to as a unique constraint. There can not be any duplicate values for the primary key column. The primary key is defined in this manner so that the database engine knows how to locate the record you are looking for. Think of this as the row name for a table. Very similar to an excel spreadsheet. If I were to give you a spreadsheet with no row numbers on it and asked you to find a specific row you would have to scan all the rows in the sheet to find what I am asking you for. If you have a primary key (usually a number) and I ask you for row #456 and it is garunteed unique you can find it and once you found it you can stop looking because you know there is no other row #456.

So, you need to make sure your values you insert for your primary key are unique. Often times you will need to define multiple columns as your primary key if a combination of values makes a row or record unique.

Hope this helps you.

-David Sandor

|||

OK, that makes sense. But for instance lets say that I only want to have this one specific entry in my table. I am parsing a file to get the info for my table. So if I come to this value again and try to insert it, it obviously will not be allowed. However after it trys that, nothing else will be inserted into any of the other tables. So for table1 I have 2 columns. The first column has a primary key. Then I have table 2 with 4 columns, I do not have a primary key because I do not mind that records are the same. But when I parse my file for insertion into the tables, it will try the first table and since the entry is already in there it will not put anything else in the second table. It seems to finish executing the code however. I was thinking I may have needed an if that checks if its alredy in there, but I could not get that to work either.

I am guess this problem is caused by the primary key thing, because when I take it off, everything works fine. Thank you very much for the reply.

Chris

I still need help with the above issue. However I think that If I get help with this problem I will be able to figure it out myself. I am trying to find something in the database. This is what I am doing.

recSet.Open("select * from Table", ADOConn, ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic)

recSet.Find("[Name] = '" & temp(i) & "'", 0, ADODB.SearchDirectionEnum.adSearchForward, 1)

If Not recSet.Fields("Name").Value = temp(i) Then

recSet.AddNew("Name", Apps(i))

recSet.Update()

recSet.Close()

End If

This is how I have seen to do things on other sites however I can not get this to work. When I try to do the find, all I am getting is the very first entry so I assume I am doing something wrong. Any help would be greatly appreciated. Thanks.