Correct it has already started and the values you send will take effect the next time you press go.
Here it was I did in an Active Script task
DTSGlobalVariables.Parent.LogToSQLServer = true
DTSGlobalVariables.Parent.LogServerName = "MyServer"
I did not allow logging to sql server on the first run
After the first run I checked the package properties and now logging to sql server is allowed.
I checked in msdb.dbo.sysdtspackagelog and there was no rows.
I re-execute and I had a row in the msdb.dbo.sysdtspackagelog table
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com
"DougHolland" <DougHolland (AT) discussions (DOT) microsoft.com> wrote
Quote:
Hi All,
I would like to be able to dynamically change the server to which logging
occurs for a given DTS package.
For example, I have a DTS that is configured to log to Server A. I would
like to pass as a parameter Server B and have the DTS package log to Server
B. So far it seems as though this is ignored, as though logging has already
begun to Server A.
Can anyone help?
Kind Regards,
Doug |