PDF-Reporting with SQL2005 Reporting Services

Hi All,
in SQL Server Business Intelligence Development Studio the reporting output
(for SQL2005 Reporting Services) can for instance be chosen as pdf or excel.
choosing pdf as output, if the tables contain more data than one DIN-A-4
page can display the tables are continued on the next page. the table header
is fortunately also repeated on each new pdf-page.
however choosing excel as output, the whole output of one table is written
into one excel spreadsheet. even if the height of the table containing the
data is more than the height of DIN-A-4 then the table is not continued on
another spreadsheet. this leads to the unfortunate phenomenon that printing
the excel workbook (with tables higher than DIN-A-4) results in DIN-A-4
printouts in which the table header is unfortunately NOT repeated on each
new printout-page. (this is due to the fact that the tables in the
spreadsheets are highre than DIN-A-4.)
unfortunately in our case the generated pdf output can not used to be
printed, because for each report there have to made slight adjustments by
each user which cannot be processed within the reporting workflow.
hence we really need a solution to programmatically adjust the excel-output
provided by the SQL Server Business Intelligence Development Studio so that
within the excel-output the spreadsheets will have the same page breaks like
the pdf-pages within the pdf-output.
we are desperately looking for a solution for this issue. can anybody state
A) if it is either impossible or
B) if it would be possible and which steps would be involved to achieve this
aim?
thanks a lot in advance for your assistance!
best regards, janHi All,
doesn't anybody have an idea on how to generate Excel-Reportings with
SQL2005 Reporting Services (with tables in the spreadsheets that are higher
than DIN-A-4 printouts) which are printable?
Has anybody yet managed to generate Excel-Output and make this output
printable so that on each printed DIN-A-4-printout the table headers are
repeated and the tables have correct page breaks?
best regards, jan
"Jan" <no@.no.com> schrieb im Newsbeitrag
news:OEjOaBiGHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi All,
> in SQL Server Business Intelligence Development Studio the reporting
> output (for SQL2005 Reporting Services) can for instance be chosen as pdf
> or excel.
> choosing pdf as output, if the tables contain more data than one DIN-A-4
> page can display the tables are continued on the next page. the table
> header is fortunately also repeated on each new pdf-page.
> however choosing excel as output, the whole output of one table is written
> into one excel spreadsheet. even if the height of the table containing the
> data is more than the height of DIN-A-4 then the table is not continued on
> another spreadsheet. this leads to the unfortunate phenomenon that
> printing the excel workbook (with tables higher than DIN-A-4) results in
> DIN-A-4 printouts in which the table header is unfortunately NOT repeated
> on each new printout-page. (this is due to the fact that the tables in the
> spreadsheets are highre than DIN-A-4.)
> unfortunately in our case the generated pdf output can not used to be
> printed, because for each report there have to made slight adjustments by
> each user which cannot be processed within the reporting workflow.
> hence we really need a solution to programmatically adjust the
> excel-output provided by the SQL Server Business Intelligence Development
> Studio so that within the excel-output the spreadsheets will have the same
> page breaks like the pdf-pages within the pdf-output.
> we are desperately looking for a solution for this issue. can anybody
> state
> A) if it is either impossible or
> B) if it would be possible and which steps would be involved to achieve
> this aim?
> thanks a lot in advance for your assistance!
> best regards, jan
>

Pausing Log Shipping Plans

We are doing an IP Restructuring on our DR site over the weekend due to some business and management requirements.I actually have 2 questions. I have implemented log shipping plans for our databases. Which means I will have to pause (disable) my log shipping plans while this is being done and resume (re-enable) after everything is comlete.

Any insights on what else I need to do apart from these?

My second question is this. I am generating transaction log backups every 15 minutes and is averaging at 350MB (this much data every 15 minutes - not to mention that I've got around 40+ databases, all configured for log shipping just for this instance alone). My alert threshold is 45 minutes. My log shipping plan for one database starts failing probably because 15 minutes is not enough to transfer 300+MB-sized backup file over a WAN locate across the globe on a not-so-high bandwidth and restore it to the destination. Any recommendations on this apart from increasing the threshold? Your assistance is highly appreciated

Log shipping should not be affected by changing the IP addresses unless you change ones targetted directly by the log shipping jobs. For the WAN case, you can consider adding a step to compress the transaction log backups prior to copying them over the network. This typically improves the end-toend throughput over a WAN.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||

Hi Matt,

Thanks for your reply. Actually, we will be changing the IPs of the destination servers You were mentioning compressing the transaction log backups prior to copying them over the network. I am using the Database maintenance plans to define my log shipping plans. The way I see it, the copy job does a "pull" method - the destination server is the one initiating the job. How do you insert a step to compress the transaction log backup files in the database maintenance plans? I am only allowed to use "Microsoft supported" procedures as per company policy

sql