I have a SSIS 2005 package with logging turned on. The pacakge is logging to a database on the localhost. I have set up a SQL Server package configuration with the LoggingMode in the package properties checked. However, changing the value in table has no impact on the logging of the package. The package applies the setting configured in the design time of the package and then deployed. My questions are as follows: Can the logging mode successfully be set using package configurations (specifically those held in a table)? And, if so is there any resource which takes me through the steps I need to follow or anything I should watch out for? Thanks in advance, Rick

Set LoggingMode to Disabled (it's a property of the package) Or use something like this: http://blogs.msdn.com/b/mattm/archive/2010/01/05/how-do-i-disable-all-logging-on-my-packages.aspx => dtexec /f "C:\Package.dtsx" /set "\Package.Properties[LoggingMode];2" Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com

Thanks SSISJoost! I had already seen this blog but what I am trying to do is set the value in the pacakges configurations table read by the package rather than the command calling the package. Unfortunately, I do not have the same level of scope to change the code calling the package as I do of the package itself. Otherwise, I would have attempted setting the value in the call the DTEXEC. In my testing setting the value to 1 or 2 in the configuration table has no impact whatsoever. The package continues to run with the setting it was deployed with. Rick

Is it also logging when you manually disable that property it in the package? Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com

Check this link which me be helpful: http://weblogs.sqlteam.com/dmauri/archive/2006/03/27/9438.aspxNitesh Rai- Please mark the post as answered if it answers your question

Thanks Nitesh! Again I had read the blog in my search for an answer. My connection is static and not related to the connectionstring. Nonetheless, I saw that logging started before Package configuration. However, they also said that logging switched after the package configurations were applied. However, in this case it seems that the behaviour did not change but rather remained as an all or nothing depending on deployment. Thansk for the responses but I am begining to think that what I am trying to do is not possible or I am missing something obvious. Rick

How do you run your package? If you use DTExec you can turn it off with this: /set "\Package.Properties[LoggingMode];2"Arthur My Blog

At present there is a hierarchy of stored procedures which determines what is to be run and passes a series of variables into the package. I was hoping ot avoid touching this code if possible but it is starting to look like I will not have an option. I will test the set in the DTEXEC call as a stand alone to see if it works.

For info the issue seemed to caused by using a table name for the logging table that was different from the standard name created by SSIS. Once the table name was reverted to the standard name everything worked as expected.

For info the issue seemed to caused by using a table name for the logging table that was different from the standard name created by SSIS. Once the table name was reverted to the standard name everything worked as expected.