ETL Settings and Configuration
Configuring ETL Logging
The following settings are primarily intended for DataSelf support staff:
- Log file debug mode
- SQL Commands log file
SQL Log File - LOG_SCRIPT_SQL.SQL
Optional log file which shows the commands sent by the ETL to MS SQL server. These commands include: CREATE TABLE, DROP TABLE, INSERT, UPDATE, CREATE VIEW, CREATE INDEX, SELECT , etc.
When the SQL logging is turned on then commands sent to the SQL Server during every table Refresh are sent to the SQL Log File LOG_SCRIPT_SQL.SQL .
Format: Text file Saved in: <etl root>/LOG_SCRIPT_SQL.SQL
- WHERE <etl root> is the folder containing dataself.exe , metadoc.exe , etc.
Turn On/Off SQL Logging
To turn on SQL logging:
Add a ‘signal’ file named:
- <etl root>/.On
(A ‘signal’ file is a file of size 0)
To turn off SQL logging:
Delete the signal file or change it’s name to:
- <etl root>/.Off
Key words: etl sql log file logging dataself
Turning on the ETL Log File Debug Mode
Turn debug mode on and off for the log file
- ( …Program Files (x86)\DataSelf\Dataself ETL\Log xxxxxx.txt )
(Where xxxxxx is the ETL Project name and refresh batch number)
by changing the file name in
- …Program Files (x86)\DatSelf\Dataself ETL\ErrorDumps\Debugmode.on
toggle the file name between Debugmode.on and Debugmode.off
When DEBUG is ON, the regular Log xxxxxx.txt is NOT written to. Find instead a comprehensive log in the same folder, named Log xxxxxx YYYYMMDD.txt (Same log name, but with a date stamp.) These logs can get large, and may be deleted later to conserve disk space. Be sure to toggle back to Debug.off when the research is completed.