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
>

PC Hardware requirements for SQL 2005 Standard Edition

Hello,

I'm wondering if it is possible to install SQL2005 standard edition on a standard dual core pc with Win XP Pro SP2 OS.

Kindly advice.

Regards

Andy

That should be fine.

As a first part of the install process, a program will execute that will verify that the hardware and software environment will support SQL Server 2005.

To check the requirements, see this resource:

SQL Server 2005 Installation Requirements (Hardware/Software)
http://msdn2.microsoft.com/en-us/library/ms143506.aspx

|||Thank you, that should save me some cash from buying a server unit.

password cannot be saved

Hi, there;
I have a SSIS package which has SQL2005 as its destination. When I setup the connectionmanager, I'd like to use SQL authentication. But I found that the password field cannot be saved (Checkbox "Save password" is selected).Everytime I open the this package's connectionmanager, that password field is cleard. The result is that my C# application that loads that package to execute failed with "Login failed..."

Did I do something wrong or anybody know how to save that password field?

CheersThe password in a SQL-authenticated connection is considered sensitive data. SSIS wants to encrypt any sensitive data in the package (see ProtectionLevel). By default it does this with your user key. Unless you've changed the ProtectionLevel, you should be able to save the package and reopen it (as the same user) and have it preserve your password. If you're going to be opening it from an application, your best bet for ProtectionLevel is probably to use the "EncryptSensitiveWithPassword" option, which uses a password to encrypt the sensitive data. The application (and any users) will need to supply this password when opening the package.

A good alternative to storing sensitive data in the package is to read the password into the package using a Package Configuration mechanism.
|||

Thanks.

Do you mean I need another password to open my package?

Where can I set the "ProtectionLevel" in the package?

|||See the link that JayH included.|||

Thank you.

I will try.