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?
|
|
|
|
|
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Friday, March 30, 2012
Monday, February 20, 2012
Preventing schedule job to run
Hi,
I have 2 jobs schedule to run after every alternate hour. Job A runs at 1 am, 3 am, 5 am etc. and job B runs at 2 am, 4 am , 6 am.
If job A is still running I would like Job B not to start at the scheduled time. How can I achieve this?
Thanks in Advance ... jVery simply... first step in Job A could be to update a flag on the DB, last step would be to remove it. First step in Job B would be to check the flag, if present it bombs if it's not there then continue.|||If you mean to have Job B not run at all, and let Job A potentially run twice in a row, then you could do it this way:
Create a table in say the pubs database called Status (col1 varchar(10))
The first step in Job A will be to put a row into this table. The last step in Job A will be to delete the table (think of it as an on/off switch)
The first step in Job B would be a check to see if a row exists, and if it does, then select 1/0 (or any other error of your choice that will trigger the OnJobStepFailure to trigger.
Set the failure action of step 1 of Job B to be exit the job, then you are done.
Not too sure what you would have to do to get Job B to run at say 2:30 or so, if you can not have Job A run twice in a row.
Hope this helps.|||Can I disable Job B or its schedule untill job A finishes? And once it finishes can I enable it?|||Yeah, you can do that, just do the following...
USE msdb
UPDATE sysjobs
SET enabled = 1
WHERE jobid = <jobid>
to enable the job and then set it back to 0 to disable it.
Another option would be to add job B as a step of job A. And just let it always run as soon as job A finishes. Not sure if that is an option though.
Hope this helps.|||Can I disable Job B or its schedule untill job A finishes? And once it finishes can I enable it?|||Sure... use the method Kuthula posted above, only instead of a flag in a table, have job A disable job B as the first step, and then enable it as the last step. using the update to sysjobs in msdb.
I have 2 jobs schedule to run after every alternate hour. Job A runs at 1 am, 3 am, 5 am etc. and job B runs at 2 am, 4 am , 6 am.
If job A is still running I would like Job B not to start at the scheduled time. How can I achieve this?
Thanks in Advance ... jVery simply... first step in Job A could be to update a flag on the DB, last step would be to remove it. First step in Job B would be to check the flag, if present it bombs if it's not there then continue.|||If you mean to have Job B not run at all, and let Job A potentially run twice in a row, then you could do it this way:
Create a table in say the pubs database called Status (col1 varchar(10))
The first step in Job A will be to put a row into this table. The last step in Job A will be to delete the table (think of it as an on/off switch)
The first step in Job B would be a check to see if a row exists, and if it does, then select 1/0 (or any other error of your choice that will trigger the OnJobStepFailure to trigger.
Set the failure action of step 1 of Job B to be exit the job, then you are done.
Not too sure what you would have to do to get Job B to run at say 2:30 or so, if you can not have Job A run twice in a row.
Hope this helps.|||Can I disable Job B or its schedule untill job A finishes? And once it finishes can I enable it?|||Yeah, you can do that, just do the following...
USE msdb
UPDATE sysjobs
SET enabled = 1
WHERE jobid = <jobid>
to enable the job and then set it back to 0 to disable it.
Another option would be to add job B as a step of job A. And just let it always run as soon as job A finishes. Not sure if that is an option though.
Hope this helps.|||Can I disable Job B or its schedule untill job A finishes? And once it finishes can I enable it?|||Sure... use the method Kuthula posted above, only instead of a flag in a table, have job A disable job B as the first step, and then enable it as the last step. using the update to sysjobs in msdb.
Subscribe to:
Posts (Atom)