Wiki

Scale Your Enterprise

User Tools

Site Tools


bw:sql_command_tool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bw:sql_command_tool [2020/12/14 17:35]
akoehler [SQL Tools]
bw:sql_command_tool [2022/08/02 10:35] (current)
akoehler [SQL System Variables]
Line 16: Line 16:
 The following pages contain additional information that may be helpful with the development of Bizweaver workflows using the SQLCommand tool. The following pages contain additional information that may be helpful with the development of Bizweaver workflows using the SQLCommand tool.
  
-  * [[bw:global_connections|Global Connections]]+  * **[[bw:global_connections|Global Connections]]**
  
 ====== Before You Begin ====== ====== Before You Begin ======
Line 59: Line 59:
     - When variables are used, they are subject to standard syntax rules regarding text vs. numeric values. This means that text variables MUST be enclosed in single quotes.     - When variables are used, they are subject to standard syntax rules regarding text vs. numeric values. This means that text variables MUST be enclosed in single quotes.
  
-The following image shows same SELECT statement as illustrated above, but with a variable in the WHERE clause.+The following image shows the same SELECT statement as illustrated above, but with a variable in the WHERE clause.
  
 {{  :bw:sqlimage2.png?411x72  }} {{  :bw:sqlimage2.png?411x72  }}
  
 +
 +<WRAP center round important>
 +When saving a workflow or opening the SQL/HANA tool or the workflow, the reader command type will validate the written query. This executes the query against the connected database. **There is the ability to have Non-query commands written using the Reader command type. This will execute the statement against the database. If a Create, Update, Insert, Truncate or Delete (any SQQL/HANA statement that affects a change to any data) is written, the command will execute and be run against the connected database if the workflow is saved or the tool or workflow is opened**
 +</WRAP>
 ===== Non-Query (SQL Server only) ===== ===== Non-Query (SQL Server only) =====
  
Line 132: Line 136:
 Click the green <color #22b14c>Run</color> link to execute tests.  If you click the "Test Run" link again the results will revert to the statement in the [SQL] tab. Click the green <color #22b14c>Run</color> link to execute tests.  If you click the "Test Run" link again the results will revert to the statement in the [SQL] tab.
 </WRAP> </WRAP>
 +
 +
 +====== SQL System Variables ======
 +
 +^ Name           ^ Description         ^
 +| CommandType       | The command type chosen in the SQL tool ex. Reader, Non-Query      |
 +| DataSourceFields |The fields pulled from the data source will only show up when executing the query in the SQL tool and not during a test run|
 +| DataSourceResultsTable         | The results from executing the query in the workflow. Will only show up when executing the query in the SQL tool and not during the test run      |
 +| QueryString         | The current query that is being executed     |
 +| SQLCommand        | Used for an older version of Bizweaver no longer returns a value    |
 +| SQLResultsCount         | The total amount of records that were retrieved during a query       |
 +|StepMessage       | During a failure the reason for failure will be populated here     |
 +| StepStatus        | True or False     |
 +
  
 ======SQL Tips====== ======SQL Tips======
bw/sql_command_tool.1607985334.txt.gz · Last modified: 2020/12/14 17:35 by akoehler