IDTSLogging.Log Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Writes the log entry.
public:
void Log(System::String ^ eventName, System::String ^ computerName, System::String ^ operatorName, System::String ^ sourceName, System::String ^ sourceGuid, System::String ^ executionGuid, System::String ^ messageText, DateTime startTime, DateTime endTime, int dataCode, cli::array <System::Byte> ^ % dataBytes);
public void Log (string eventName, string computerName, string operatorName, string sourceName, string sourceGuid, string executionGuid, string messageText, DateTime startTime, DateTime endTime, int dataCode, ref byte[] dataBytes);
abstract member Log : string * string * string * string * string * string * string * DateTime * DateTime * int * Byte[] -> unit
Public Sub Log (eventName As String, computerName As String, operatorName As String, sourceName As String, sourceGuid As String, executionGuid As String, messageText As String, startTime As DateTime, endTime As DateTime, dataCode As Integer, ByRef dataBytes As Byte())
Parameters
- eventName
- String
The event calling the log entry.
- computerName
- String
The name of local computer.
- operatorName
- String
The user account.
- sourceName
- String
The object that is the source of the event.
- sourceGuid
- String
The GUID of the task.
- executionGuid
- String
The GUID of the specific execution of the package, used to distinguish multiple executions of the same package.
- messageText
- String
The text to write in the log.
- startTime
- DateTime
The start time of the event.
- endTime
- DateTime
The end time of the event.
- dataCode
- Int32
Numeric data field.
- dataBytes
- Byte[]
A byte array field for binary large objects (BLOBs).
Remarks
The primary method for logging is the Log method. All events logged using this method will be subject to filtering by the LoggingOptions object. However, you achieve certain performance gains by conditioning the calls to Log based on whether logging is enabled, which is done by checking the Enabled status. This enables you to save the time it would take to compose the arguments and the method call overhead.