May 31, 2006 at 7:36 am
Trying to setup dynamic connections for my DTS pkgs to establish dynamic connection to our ErrorLogFile logging location. I found the following tip:
Setting Log File Dynamically in SQL Server 2000 DTS - Very often there are cases when we want to have our DTS package to log error at a different path or file. This can very easily be achieved in the following way...
1. Create INI file containing ErrorLogFile location
[ErrorLogFile]
ErrorLogFile=\\MyServer\DTSLogs\MyDTSpkgLogName.txt
2. Read the log file path from the INI file and store it to a global variable called ErrorLogFile using the Dynamic Properties Task.
3. Set the Package's error log to the new value using ActiveX scripting.
set oPackage = DTSGlobalVariables.Parent
oPackage.Properties("LogFileName").Value = DTSGlobalVariables("ErrorLogFile").Value
Question: We have over 200 DTS pkg's. We'd like to define a single INI file containing all connection info. Is it legal to setup multiple ErrorLogFile entries in my INI file?
[ErrorLogFile_1]
ErrorLogFile=\\MyServer\DTSLogs\MyDTSpkg_1_LogName.txt
[ErrorLogFile_2]
ErrorLogFile=\\MyServer\DTSLogs\MyDTSpkg_2_LogName.txt
[ErrorLogFile_3]
ErrorLogFile=\\MyServer\DTSLogs\MyDTSpkg_3_LogName.txt
June 1, 2006 at 7:16 am
answer is yes
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply