Advanced ETL Log Files?

Has any one developed a way to import the Tr_*.log files they'd be willing to share. I'd like to load them into SQL.

Hi

Tr*.log files a just tab delimited text files (utf8 Encoded)
So you should be able to load them without any problems.
Just copy them into different directory first and load them from there.
The reason for it when you run your transformation it will create another tr file in the same directory.
This file will be locked until transformation is completed therefore it will fail.

There is another alternative, you can redirect all log messages using LOG object and load them directly into the sql database

www.etl-tools.com/wiki/aetl:processing_data:working_with_log

This seems really cool. When I run it I kicked out of Advanced ETL. It seems like it's trying to read the current log file or perhaps there's an empty log file.

Looking at what got loaded into SQL, there's no way to prevent duplicate entries. I guess I could purge log files easily enough.

That could we a bug in our software (no one is perfect)

Also it is very important uptick write to log, for the object selected otherwise it will definitely fail




Also, default repository has an example called log redirect that ma be very very useful for you

And can you provide us with table creation script, so we can try to reproduce the problem in the office

Here is the SQL table I am using.

USE [DB_87661_demo22]
GO

/****** Object: Table [dbo].[ETL_ExecutionLog] Script Date: 3/21/2016 7:34:12 AM ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[ETL_ExecutionLog](
[LogID] [int] IDENTITY(1,1) NOT NULL,
[Status] [nchar](25) NULL,
[ObjectName] [nchar](25) NULL,
[ObjectType] [nchar](25) NULL,
[FunctionName] [nchar](25) NULL,
[FunctionType] [nchar](25) NULL,
[FieldNo] [nchar](25) NULL,
[FieldName] [nchar](80) NULL,
[DataType] [nchar](25) NULL,
[ValueBefore] [nchar](255) NULL,
[ValueAfter] [nchar](255) NULL,
[ExecutionResultType] [nchar](25) NULL,
[ActionTaken] [nchar](25) NULL,
[MessageText] [nchar](255) NULL,
CONSTRAINT [PK_ETL_ExecutionLog] PRIMARY KEY CLUSTERED
(
[LogID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]

GO

Status update: we have reproduced the problem