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
|||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
No comments:
Post a Comment