Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To save memory, you can use the @run command. If you try to load a very large file, DbVisualizer suggests using the @run command automatically:

Image RemovedImage Added

 


The @run command executes a script file by only loading one statement at a time, minimizing the memory requirements. A related command is the @cd command for changing the current directory.

...

Code Block
languagenone
@run monthlyReport ${month||20102021-0501-0514||Date||noshow}$ ${dept||HR||String||noshow}$ 

Even though the @run command reads one statement at a time from the file, there are other parts of the execution process that require the whole file to be read before the statements can be executed: parsing the script for variables, parameter markers, and restricted commands, as well as counting all statements in order to provide progress information. When you run a script that is large enough (more than 10 MB) for these things to potentially cause memory problems and slow down the processing, DbVisualizer gives you a chance to turn off this preprocessing and progress reporting so that the statements instead can be executed directly as the are read from the file, one at a time.

Image RemovedImage Added

To ensure that you don't have any problems running scripts this large we strongly recommend that you click Continue w/o Preprocessing, thereby disabling all variable, parameter and restricted commands processing. Only click Continue Normally if you know for sure that you have enough memory available and have adjusted your installation so that DbVisualizer can use it. With the preprocessing disabled, you should be able to execute scripts of any size (we have tested with scripts as large as 4 GB).

...