Minq Software developed DBVisualizer, and it was to their Web site that I was pointed when I clicked the DBVisualizer link in.
It is built on Java technology and therefore uses Java Database Connectivity (JDBC) drivers as its connectivity mechanism. There you find Stop on Error, Stop on SQL Warning and Stop on No Rows check boxes for enabling these features in all SQL Commander tabs.Īlternatively, you can use DbVisualizer client side commands to enable or disable these features in a script. DBVisualizer is a cross-platform database tool used for all major relational databases. Open Tools->Tool Properties and select the SQL Commander category under the General tab. You can control whether subsequent statements should be executed when a statement results in an error, a warning or returns or affects no rows. Control Execution after a Warning or an Error This is useful when executing complex SQL statements such as CREATE STORE PROCEDURE (or similar) where statement splitting on semicolon must not be done as with SQL Commander->Execute and SQL Commander->Execute Current. The SQL Commander->Execute Buffer sends all of the content in the SQL editor to the database in a single run. This will highlight the current statement without executing it. If you are unsure what the boundaries are for the current statement then use Edit->Select Current Statement. This means that the caret may be after the statement delimiter as long as there is no other statement on the same line. This is a useful feature when you have several SQL statements in the SQL editor and you just want to execute one or a few of the statements.Įxecute Current determines the actual statement by parsing the editor buffer using the standard statement delimiters.The current statement is the statement containing the caret or that ends on the line with the caret. If you select a statement in the SQL editor and choose SQL Commander->Execute main menu option, only the selected statement is executed. If there are several results and an error occurred in one of them, the Log tab is automatically displayed to indicate the error. The result of the execution is displayed in the results area based on the type of results result(s) that are returned.
For example " go 5" will then execute the statement 5 times. The "go" command supports setting the number of times the statement should be executed. Usually semicolon " " following the actual statement and "go" which should be the only command on a new line directly after the statement that should be executed.
The SQL Commander does not support executing SQLs for multiple database connections in one batch.ĭbVisualizer uses the delimiters specified in the Tool Properties dialog, in the SQL Commander/Statement Delimiters category under the General tab, to separate one statement from the next. The currently selected Database Connection is used for all statements. The SQL Commander executes the statements one by one and indicates the progress in the log area. Use the SQL Commander->Execute main menu operation to execute the SQL in the SQL Commander editor. Execute a Script with Multiple Statements