AppSecInc. MSI Extensions

ODBQ.exe exposes functionality provided by the Wix::Extensions::DataSource::ODBCExecute and the Wix::Extensions::DataSource::ODBCExecuteFile MSI extensions to the command line.

Usage:

USAGE:

   ODBQ.exe  {--sql <string> ... |--file <file> ... |--datafile <datafile> ...}
             [--outputfile <file>] 
             [--type <string>|--delimiter <string>]
             [--connectionstring <string>]
             [--database <string>] 
             [--flattenonly]
             [--noresults] [--nosql] [--nologo] [--rawoutput]
             [--] [--version] [-h]


Where:

   --sql  (accepted multiple times)
     (OR required)  SQL query to execute, eg. "SELECT @@VERSION".
         -- OR --
   --file, -f  (accepted multiple times)
     (OR required)  File(s) containing SQL statements, may be a wildcard.
         -- OR --
   --datafile  (accepted multiple times)
     (OR required)  XML file containing data sets to insert.

   --outputfile, -o
     Xml output file for messages and dataset results.

   --type, -t
     type of emulated command-line tool. May be on of (case-incensitive):
         SqlServer, MSSQL, osql, sqlcmd, tsql  - for MS SQL Server
         Oracle, sqlplus, sql*plus - for Oracle.
     Delimiter for splitting SQL are selected according to type,
     insert commands are supported.
     Default is SqlServer.
         -- OR --
   --delimiter
     Delimiter for splitting SQL statements, eg. "GO". 
     Note: delimiter is case-nsensitive, recognized only at the beginning of line

   --connectionstring
     Driver-specific connection string to use to connect to the server,
     eg. "Driver=SQL Server;Server=.;Trusted_Connection=yes"

   --database
     Default database name, added to the connection string.

   --flattenonly
     Don't execute sql, only substitute all included files
     and print resulting flattened sql file either to standard output
     or to the <outputfile> if specified

   --noresults
     Suppress results output to console.

   --nosql
     Suppress SQL statements output to console.

   --nologo
     Suppress logo and messages, raw output only.
     
   --rawoutput
     Output results into file in 'raw' format (rows \n-separated, 
     columns \t-separated) rather then in xml format.
     Also switches off output of column headers and row/column counts.

   --,  --ignore_rest
     Ignores the rest of the labeled arguments following this flag.

   --version
     Displays version information and exits.

   -h,  --help
     Displays usage information and exits.

Examples:

Executing a statement on a local SQL server.

$ odbq.exe --sql "PRINT @@VERSION"

ODBQ 1.0.2758.0 - Copyright (c) Application Security Inc.

- Connecting with "Driver=SQL Server;Server=.;Trusted_Connection=yes;""
> PRINT @@VERSION
< Microsoft SQL Server 2005 - 9.00.3068.00 (Intel X86)
        Feb 26 2008 18:15:01
        Copyright (c) 1988-2005 Microsoft Corporation
        Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 3)

Executing a statement and writing results to an xml output file.

$ odbq.exe --sql "SELECT @@VERSION" --outputfile Version.xml

ODBQ 1.0.2758.0 - Copyright (c) Application Security Inc.

- Connecting with "Driver=SQL Server;Server=.;Trusted_Connection=yes;""
> SELECT @@VERSION
< 1x1
Column1
-------
Microsoft SQL Server 2005 - 9.00.3068.00 (Intel X86)
        Feb 26 2008 18:15:01
        Copyright (c) 1988-2005 Microsoft Corporation
        Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
- Writing "F:\source\commoncomponents\Msi\trunk\target\Debug\bin\Version.xml"

The resulting version.xml is:

<Data>
 <DataSet columns="1" rows="1">
  <Query>SELECT @@VERSION</Query> 
  <RowSet>
   <Row>
    <Column1 type="nvarchar">Microsoft SQL Server 2005 - 9.00.3068.00 (Intel X86) Feb 26 2008 18:15:01 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 6.0 (Build 6001: Service Pack 1)</Column1> 
   </Row>
  </RowSet>
  <Messages /> 
 </DataSet>
</Data>

Importing data from xml.

You can use the files exported from ODBQ.exe with --outputfile with some modifications: you must add the table name to the RowSet node.

<Data>
 <DataSet columns="6" rows="6">
  <RowSet table="MyDatabase.dbo.SomeTable">
   <Row>
    <EntryID type="integer">1</EntryID> 
    <Key type="nvarchar">key</Key> 
    <Value type="ntext">value</Value> 
    <Value2 type="text">NULL</Value2> 
    <Value3 type="varchar">NULL</Value3> 
    <SomeNumber type="integer">2</SomeNumber> 
   </Row>
   <Row>
    <EntryID type="integer">2</EntryID> 
    <Key type="nvarchar">key1</Key> 
    <Value type="ntext">value1</Value> 
    <Value2 type="text">NULL</Value2> 
    <Value3 type="varchar">NULL</Value3> 
    <SomeNumber type="integer">2</SomeNumber> 
   </Row>
  </RowSet>
 </DataSet>
</Data>

$ odbq.exe --datafile Data.xml --outputfile Results.xml

The resulting out xml contains any messages from the ODBC driver and the number of rows affected.

<Data>
 <DataSet table="MyDatabase.dbo.SomeTable" rowsaffected="2">
  <Messages /> 
 </DataSet>
</Data>

Executing multiple statements with a connection string specified.

Note that if you choose to mix --sql and --file options, SQL queries are executed first, followed by execution of file contents.