Package Configurations - some requests

To any Microsoft SSIS developers reading this forum, some requests:

1) do NOT allow a package to run if it has "package configurations" enabled and one or more XML files with configurations cannot be found;

2) update the properties window with the properties read from the "package configurations";

3) allow relative paths in the "package configurations" locations (relative to the package location)

Thank you :-)

Tom,

If you want to make requests for future enhancements then do so at Microsoft Connect.

Regarding point #1, quite a few people have asked for this but then alot of people during the beta timeframe asked for the behaviour to be the way it is now. You just can't please all of the people all of the time

-Jamie

|||

Hi Jamie,

Thanks for the link - will use (abuse) it.

Cheers,
Tom

Ownership chain question

HI,
MS SQL 7.0 on NT 4 (clustered)
Our developers use Infomaker to create many end-user's reports. They are
used to creating many Stored Proc and many "intermediate" tables instead of
creating "pure" Infomaker Reports. Report's components are often modified
directly on Production database during office hours by thoses developpers.
All of our end-user's reports are going to be rebuilt with Crystal Report.
Is it a good idea to ask our developpers to locate thoses end-user's reports
components into another databases instead of mixing DATA and REPORTS
component into the same Production Database ? (I know that we must take care
of Ownership chain)
Thank you
Danny"Danny Presse" <dpresse@.congresmtl.com> wrote in message
news:eA6M9CfXDHA.2476@.tk2msftngp13.phx.gbl...
> HI,
> MS SQL 7.0 on NT 4 (clustered)
> Our developers use Infomaker to create many end-user's reports. They are
> used to creating many Stored Proc and many "intermediate" tables instead
of
> creating "pure" Infomaker Reports. Report's components are often modified
> directly on Production database during office hours by thoses developpers.
> All of our end-user's reports are going to be rebuilt with Crystal Report.
> Is it a good idea to ask our developpers to locate thoses end-user's
reports
> components into another databases instead of mixing DATA and REPORTS
> component into the same Production Database ? (I know that we must take
care
> of Ownership chain)
Yes. Definitely.
Give them guest access only to the production database (you need this for
cross-database views to work).
Create views in their database that proxy over to the production database.
This keeps them from having to bind to the database name of the production
database.
David