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

Payroll Security

Dear all,
I want to use SQL 2005 as back end for payroll software.
If I want the administrator can not see the employee salary, how to use the
built in encryption feature ?
Thanks.
VensiaOne of the ways to do this would to use a trigger on the table that contains
the information. In this CLR Trigger, call the native encryption functions.
Shaun McDonnell

> Dear all,
> I want to use SQL 2005 as back end for payroll software.
> If I want the administrator can not see the employee salary, how to
> use the
> built in encryption feature ?
> Thanks.
> Vensia
>

Payroll Database Security

Dear all,
I have a payroll database and only payroll user can see the data. Can I
prevent the SQL server administrator accessing the database ?
Thanks before.
Regards,
VensiaHi
No, not natively. Get your vendor to support SQL Server 2005 when it is
released 7 November 2005 and then each column can be encrypted in the DB.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vensia" wrote:

> Dear all,
> I have a payroll database and only payroll user can see the data. Can I
> prevent the SQL server administrator accessing the database ?
> Thanks before.
> Regards,
> Vensia
>
>|||Currently, how payroll software vendor protect the database from being
accessed by administrator except the HR user ?
Thx.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:FCB592B0-6112-4567-8B01-EB7DA1150331@.microsoft.com...[vbcol=seagreen]
> Hi
> No, not natively. Get your vendor to support SQL Server 2005 when it is
> released 7 November 2005 and then each column can be encrypted in the DB.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Vensia" wrote:
>

patching

What is the differnce between a Service Pack and Security Patches that come
out over time? What about Hot Fixes? Is Microsoft the only sources of
patches? Should I test the patch on a demo server before I place it in
production or should I just trust Microsoft?Hi
A SP is a fully end to end tested release that implements fixes and
enhancements to the base product. SP's are cumulative (then contain all
prior SP's fixes plus more).
A Security patch is a hotfix that addresses high priority fixes that if not
applied, could lead to compromised security.
A Hotfix is an update, issued to fix a specific problem that somebody had
encountered and Microsoft needs to fix as it could affect other users. A
Hotfix has limited support and does not have the massive amount of
regression testing as a Service Pack would as it is not possible in the
short time frames needed.
NEVER get a hotfix/SP/Security pack from any other source than Microsoft.
Microsoft never e-mails files either. There is always a link to their site
from where you can download it. You never know who has tampered with the
files if you don't get them yourself from MS.
With any release, always put it on test servers before production ones.
Functionality can change or behavior you were used to could be altered in a
way that your applications were not expecting.
www.microsoft.com/sql
www.microsoft.com/security
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:FECD7708-9C36-4810-9EF8-D011ADB6B021@.microsoft.com...
> What is the differnce between a Service Pack and Security Patches that
come
> out over time? What about Hot Fixes? Is Microsoft the only sources of
> patches? Should I test the patch on a demo server before I place it in
> production or should I just trust Microsoft?|||Hello Mike,
thanks for the answer. I am getting flack for wanting to test Service Packs
before they go into production.
Rich
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> A SP is a fully end to end tested release that implements fixes and
> enhancements to the base product. SP's are cumulative (then contain all
> prior SP's fixes plus more).
> A Security patch is a hotfix that addresses high priority fixes that if no
t
> applied, could lead to compromised security.
> A Hotfix is an update, issued to fix a specific problem that somebody had
> encountered and Microsoft needs to fix as it could affect other users. A
> Hotfix has limited support and does not have the massive amount of
> regression testing as a Service Pack would as it is not possible in the
> short time frames needed.
> NEVER get a hotfix/SP/Security pack from any other source than Microsoft.
> Microsoft never e-mails files either. There is always a link to their site
> from where you can download it. You never know who has tampered with the
> files if you don't get them yourself from MS.
> With any release, always put it on test servers before production ones.
> Functionality can change or behavior you were used to could be altered in
a
> way that your applications were not expecting.
> www.microsoft.com/sql
> www.microsoft.com/security
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:FECD7708-9C36-4810-9EF8-D011ADB6B021@.microsoft.com...
> come
>
>|||Hi
SP4 will break applications if they use XP functions that access the
registry. How much fun will you have if your app uses it and it dies because
of this?
If they don't accept that you need to test compatibility, then maybe you are
working for the wrong company.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:E9805C2D-3522-4194-BCB4-58307D1E8422@.microsoft.com...
> Hello Mike,
> thanks for the answer. I am getting flack for wanting to test Service
Packs[vbcol=seagreen]
> before they go into production.
> Rich
> "Mike Epprecht (SQL MVP)" wrote:
>
not[vbcol=seagreen]
had[vbcol=seagreen]
Microsoft.[vbcol=seagreen]
site[vbcol=seagreen]
in a[vbcol=seagreen]
of[vbcol=seagreen]
in[vbcol=seagreen]|||Always test service packs before putting them into production. Although
service packs go through more testing than hotfixes there are so many
different environments out there that unless you test it in your specific
environment you can't be sure you're not going to hit an issue. Certainly in
our environment we have come across some very weird bugs just because of how
we have our servers configured (weirdest one yet was down to having an
affinity mask that was a multiple of 7 <g> )
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:E9805C2D-3522-4194-BCB4-58307D1E8422@.microsoft.com...[vbcol=seagreen]
> Hello Mike,
> thanks for the answer. I am getting flack for wanting to test Service
> Packs
> before they go into production.
> Rich
> "Mike Epprecht (SQL MVP)" wrote:
>

Password security

Have SQL 7.0 running on a Windows 2000 server. Users
access the database on a front end client that utilizes
SQL authentication. I see no password restriction
properties anywhere. I need to set some restrictions,
such as password expiration in 90 days, unique password
requirements, and minimum password lengths. Where do I
set up these restrictions? I can't find anything.Those options are not availble for SQL logins in SQL 7 or 2000. Odds are
we'll have it for the next major release.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.