PDF Rendering: What about metadata and security?

Is there any way when rendering reports into PDF, to specify metadata such
as Title, Author, Subject and Keywords? And... what about security
properties? Allow/Prevent document printing / changing document / extract
contents / etc.
Regards.Sorry, this is not supported.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Lightman Robles" <dlightman@.NOSPAMiname.com> wrote in message
news:O7tIKwLTFHA.4056@.TK2MSFTNGP15.phx.gbl...
> Is there any way when rendering reports into PDF, to specify metadata such
> as Title, Author, Subject and Keywords? And... what about security
> properties? Allow/Prevent document printing / changing document / extract
> contents / etc.
> Regards.
>|||Is it expected to be supported on SQL Server 2005 version of Reporting
Services?
Regards.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> escribió en el
mensaje news:%23WXtIyTTFHA.2548@.TK2MSFTNGP14.phx.gbl...
> Sorry, this is not supported.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "David Lightman Robles" <dlightman@.NOSPAMiname.com> wrote in message
> news:O7tIKwLTFHA.4056@.TK2MSFTNGP15.phx.gbl...
>> Is there any way when rendering reports into PDF, to specify metadata
>> such as Title, Author, Subject and Keywords? And... what about security
>> properties? Allow/Prevent document printing / changing document / extract
>> contents / etc.
>> Regards.
>>
>|||No. It is under consideration for a future release.
Nonetheless, in the meantime ISVs could implement their own custom PDF
rendering extension which supports it. Or you could look into a custom
solution with post processing of the PDF files e.g. using SDKs for changing
PDF files.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Lightman Robles" <dlightman@.NOSPAMiname.com> wrote in message
news:OjY5Sv6TFHA.2420@.TK2MSFTNGP12.phx.gbl...
> Is it expected to be supported on SQL Server 2005 version of Reporting
> Services?
> Regards.
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> escribió en el
> mensaje news:%23WXtIyTTFHA.2548@.TK2MSFTNGP14.phx.gbl...
>> Sorry, this is not supported.
>>
>> -- Robert
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "David Lightman Robles" <dlightman@.NOSPAMiname.com> wrote in message
>> news:O7tIKwLTFHA.4056@.TK2MSFTNGP15.phx.gbl...
>> Is there any way when rendering reports into PDF, to specify metadata
>> such as Title, Author, Subject and Keywords? And... what about security
>> properties? Allow/Prevent document printing / changing document /
>> extract contents / etc.
>> Regards.
>>
>>
>sql

Path to configuration files

Can someone tell me why path to the configuration file couldn't be relative to the package? When I try to use relative path (i.e. do not specify full path to the configuration file) package then run from BIDS looks for configuration file in the solution folder instead of package's folder (project folder).

Is there ane way to force package use same folder to search for caonfiguration files?

Thanks

No unfortunately not. Maybe this is something you could request at http://connect.microsoft.com/sqlserver/feedback

I don't know the rationale for not allowing relative paths but I would guess its because how would you know what the path relative to a package is if the package is stored in SQL Server? If you look at it from this perspective absolute paths make more sense.

-Jamie

|||

Ok. I'll try to live with it now=/

It seems very srange to me why no one at MSFT even think about of deployment process of ETL solutions to end-user's environment

|||

So, by the way, may be you know where package will search for configuration files if package stored in "program files\my company\my solution" folder and exeuted by dtexec in the way like this:

dtexec /file:"program files\my company\my solution\mypackage.dtsx"?

|||

Andrey Makarov wrote:

Ok. I'll try to live with it now=/

It seems very srange to me why no one at MSFT even think about of deployment process of ETL solutions to end-user's environment

Well, they did think about it. They just got it wrong that's all :) That is to say, there is a bug.

-Jamie

|||

Andrey Makarov wrote:

So, by the way, may be you know where package will search for configuration files if package stored in "program files\my company\my solution" folder and exeuted by dtexec in the way like this:

dtexec /file:"program files\my company\my solution\mypackage.dtsx"?

No. Perhaps you can tell me?

-Jamie