How To Make Logging Configuration-based Only
i need make logging location independent through use of configuration files, cannot seem work.
goal: need log packages run-time determined database. location not know @ development , deployment time. in fact logging sites available @ development & testing not available @ run-time.
what have done:
first, added log provider connected through ole db connection manager. then, enabled logging on package , independently on of executables in package. ran , works fine, logging shows in right place, etc.
secondly, disabled pre/post validation logging , set objects delayvalidation=true because packages spew errors in ide when try move them different environments.
thirdly, setup indirect configuration file loads cm's connection string vairable , changed cm add expression variable connection string property. tested , still works ok.
fourthly, set connection string variable invalid server name simulate run-time startup conditions of package (remember indirect configuration file still has correct server name). when try debug/test package throws error cm cannot connect logging database. no logging occurs , nothing runs (i had breakpoints in package preexecute , prevalidate handlers)
fifthly, disabled package loggingmode. still fails.
sixthly, change invalid cm location valid secondary database. now, package logging still off package runs fine, package not log, executables do. logging shows in primary logging db (from config file), package did create logging table in secondary db (but no rows logged).
seventh, create variable expressed package loggingmode property , loaded configuration file. set "2" (disabled) in ide, "1" (enabled) in config file. figure way, logging turned off until cm has been setup config file values. however, when debug/test it, fails same failure connect database , not run.
well, out of ideas. please, please help.
rbarryyoung
goal: need log packages run-time determined database. location not know @ development , deployment time. in fact logging sites available @ development & testing not available @ run-time.
what have done:
first, added log provider connected through ole db connection manager. then, enabled logging on package , independently on of executables in package. ran , works fine, logging shows in right place, etc.
secondly, disabled pre/post validation logging , set objects delayvalidation=true because packages spew errors in ide when try move them different environments.
thirdly, setup indirect configuration file loads cm's connection string vairable , changed cm add expression variable connection string property. tested , still works ok.
fourthly, set connection string variable invalid server name simulate run-time startup conditions of package (remember indirect configuration file still has correct server name). when try debug/test package throws error cm cannot connect logging database. no logging occurs , nothing runs (i had breakpoints in package preexecute , prevalidate handlers)
fifthly, disabled package loggingmode. still fails.
sixthly, change invalid cm location valid secondary database. now, package logging still off package runs fine, package not log, executables do. logging shows in primary logging db (from config file), package did create logging table in secondary db (but no rows logged).
seventh, create variable expressed package loggingmode property , loaded configuration file. set "2" (disabled) in ide, "1" (enabled) in config file. figure way, logging turned off until cm has been setup config file values. however, when debug/test it, fails same failure connect database , not run.
well, out of ideas. please, please help.
rbarryyoung
rbarryyoung said:
rbarryyoung
thirdly, setup indirect configuration file loads cm's connection string vairable , changed cm add expression variable connection string property. tested , still works ok.
rbarryyoung
i think there problem. have use package configuration set connection string property of cm directly. not use ssis variable , expression that. has order of events when package invoked. still have provide valid value @ design time (when working in bids, is).
rafael salas | don’t forget mark post(s) answered question http://rafael-salas.blogspot.com/
SQL Server > SQL Server Integration Services
Comments
Post a Comment