sql server - Why is SSIS job using connection manager parameters in package to validate instead of configuration file values? -
i have ssis package run sql server agent job configuration file specified in job contains servers , initial catalogs connection managers of package. running fine in production , using servers , databases specified in configuration file when package runs. however, when changed table in dev environment, production package failed validation because apparently validating package based on dev database specified in connection managers in package (which naturally point dev environment) , using config file values when running package. absurd, of course. how stop doing that? should both validate , run using config file parameters, otherwise point of using config files?!
i should clarify production job ran without problems after generating errors internally, have error handling task emails me details of errors package raises during execution. getting emails of failures packages didn't encounter errors when ran not thing.
i using ssis in sql server 2008 r2 , both ssis package , xml configuration file stored in file system. in advance.
Comments
Post a Comment