EVL – ETL Tool

Products, services and company names referenced in this document may be either trademarks or registered trademarks of their respective owners.

Copyright © 2017–2023 EVL Tool, s.r.o.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.

Table of Contents


(since EVL 2.7)

Run SQL or sqlite3 commands from stdin or <f_in> and write result into stdout or <f_out>. It returns output from ‘sqlite3’ as is, so for quering the table to get formatted EVL output use ‘Readsqlite’ or ‘evl readsqlite’.

Path to the database file is taken from environment variable ‘$EVL_SQLITE_DATABASE’, unless <db_file> is specified.


is to be used in EVS job structure definition file. <f_out> is either output file or flow name.

evl runsqlite

is intended for standalone usage, i.e. to be invoked from command line and writing records to standard output.

EVD and EVS are EVL definition files, for details see evl-evd(5) and evl-evs(5).


  <f_in> <f_out> [--dbname=<db_file>] [--sqlite=<sqlite_options>]

evl runsqlite
  [--dbname=<db_file>] [--sqlite=<sqlite_options>]

evl runsqlite
  ( --help | --usage | --version )



path to the SQLite database file; if this option is not used, database file is taken from environment variable ‘$EVL_SQLITE_DATABASE’.


all <sqlite_options> is provided to ‘sqlite’ utility.

Standard options:


print this help and exit


print short usage information and exit

-v, --verbose

print to stderr info/debug messages of the component


print version and exit