The following windows can save settings files that tell you how to run them from the command line:

  • Analyze All Objects
  • Compare Databases
  • Compare Schemas
  • Database Health Check
  • HTML Schema Doc Generator
  • Generate Database Script
  • Generate Schema Script
  • Rebuild Multiple Objects
  • Save As (Save Grid Contents)

There is also a command line option to run a script:

"toadpath\toad.exe" CONNECT=user/pwd@database filename /EXEC


  • "toadpath" is the directory path for the TOAD executable
  • "filename" is the name of the script file

Note that Quest ScriptRunner (QSR) can also run scripts from the command line. It uses the same syntax as SQL*Plus for this:

"qsrpath\qsr.exe" user/pwd@database @filename 

where "qsrpath" is the directory path for the QSR executable. If your script contains an "exit" command, then QSR will close as soon as it is finished.


You can use the Automation Designer in Toad to schedule many, many tasks within Toad. Please see the online Help within the tool, and there is a video describing the process here:


Action Parameter files

As of version 10, Actions can now accept parameter files. They are in INI format. Right click on an Action/App in Automation Designer and choose "Create Parameter file" to build an INI file based on the current Action properties. It will create property=value pairs for the things which can be overridden. This parameter file can then be used in the Automation Designer ('Run with parameter file') or on the command line by using a pipe to separate the Action/App name from the filename. For example:

toad.exe -a "App->Export Dataset1 | c:\data files\exportDataset1.ini"

You will know which Actions can generate/read an INI file by whether or not the 'Create parameter file' popup menu item in Automation Designer is enabled.


Here is a sample section from an INI file which shows an Execute Script Action:

Name=Execute Script1
Type=Execute Script
Output=1 {1=SingleFile, 2=SeparateFile, 3=Clipboard, 4=Discard}
Output Location=C:\some folder\output.txt

[47] is an internal identifier. "Name" and "Type" are only for your use, to find your Action within a longer App INI file. Each Actions INI section will be unique to that Action, and in the case of things like enumerated types, will include explanatory notes embedded within the line itself. In this example of 'Execute Script,' two connections are specified. This will override the bound connection of the Action. If that line wasn't there, the bound connection would be used.

The order of precedence for which connections get used:

  1. Those specified on command-line always override everything else
  2. If 1 is not present, those specified in an INI file are considered next
  3. Finally, the connection bound to the Action is used if none are in 1 or 2

Start the discussion at