Page History
...
The SQL database activities are not intended and not usually suitable for high-throughput, high-volume database operations. Rather they provide a simple means to complete a business process integration solution that may not otherwise have been possible, with some simple, low-volume database access and/or maintenance.
| Info |
|---|
It is recommended that you keep your SQL operations through these activities as simple as possible. |
| Note | ||||
|---|---|---|---|---|
|
...
LANSA Composer does not guarantee that any form of SQL statement that is valid for your target database can successfully be executed through the SQL database activities, nor that every form of SQL stored procedure can successfully be executed. |
Example Processing Sequences using the SQL database activities
...
- Use the following activities to establish or disconnect an SQL database connection:
Connect to database using SQL | |
Disconnect from database using SQL |
Use the following activities to query the database:
Query database using SQL and iterate the results~
Query database using SQL
Query database using SQL to output CSV file
Use the following activities to perfom insert, update and delete operations in the database:
Update database using SQL
Use the following activities to execute an SQL stored procedure in the database:
Execute an SQL stored procedure
Query database using an SQL stored procedure to CSV
Query database using an SQL stored procedure
Use the following activities to implement transaction control relating to any database insert, update or delete operations you have performed:
Commit a database transaction using SQL
Rollback a database transaction using SQL
Use the following activities to set the parameter values for an SQL operation:
Set parameter values for SQL operation
Set parameter values for SQL operation from CSV
Use the following activity in custom solutions to directly access the SQLServerService JSM session:
Get JSM session handle for SQL connection
| Anchor | ||||
|---|---|---|---|---|
|
When a LANSA Composer Processing Sequence run ends in error, it is often possible to restart it from the point of failure—once the cause of the failure has been corrected. This is a very powerful feature of LANSA Composer.
...
In any event, to maximize the benefit of LANSA Composer's restart capability, you should complete your SQL database operations and execute the SQL_DISCONNECT activity at the earliest opportunity. Once the SQL database connection has been closed, normal restart eligibility resumes.
...
| Note | ||||
|---|---|---|---|---|
| ||||
The FOR_EACH_SQL_QUERY activity is not restartable, irrespective of the values specified for the RESTARTELIGIBLE parameter of the SQL_CONNECT activity. |
INPUT Parameters:
DBCONFIG: Required
This parameter must specify the name of a Database Configuration that specifies the details necessary to establish the database connection.
RESTARTELIGIBLE: Optional
This parameter specifies whether the LANSA Composer processing sequence that contains this activity should remain eligible for restart while the SQL database connection remains open. The default value is YES.
...
For more information refer to Eligibility for Processing Sequence Restart above.
OUTPUT Parameters:
SQLHANDLE:
If successful, the value of this output parameter identifies the SQL connection established by this instance of the SQL_CONNECT activity. The same value must be specified as the SQLHANDLE input parameter value for all subsequent SQL database activities that are to operate on the same SQL database connection.