Database Operations with Slow Execution Phases

Appian Max Team — Thu, 18 Apr 2024 16:06:55 GMT

Current Revision posted to Article by Appian Max Team on 4/18/2024 4:06:55 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

Appian Max Team — Thu, 18 Apr 2024 16:03:44 GMT

Revision 12 posted to Article by Appian Max Team on 4/18/2024 4:03:44 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

joel.larin — Thu, 02 Nov 2023 13:31:01 GMT

Revision 11 posted to Article by joel.larin on 11/2/2023 1:31:01 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

joel.larin — Thu, 02 Nov 2023 13:29:44 GMT

Revision 10 posted to Article by joel.larin on 11/2/2023 1:29:44 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

joel.larin — Thu, 02 Nov 2023 13:29:19 GMT

Revision 9 posted to Article by joel.larin on 11/2/2023 1:29:19 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

joel.larin — Thu, 02 Nov 2023 13:26:30 GMT

Revision 8 posted to Article by joel.larin on 11/2/2023 1:26:30 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

Kim Day — Tue, 31 Oct 2023 20:53:29 GMT

Revision 7 posted to Article by Kim Day on 10/31/2023 8:53:29 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

Kim Day — Tue, 31 Oct 2023 20:47:27 GMT

Revision 6 posted to Article by Kim Day on 10/31/2023 8:47:27 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

Kim Day — Tue, 31 Oct 2023 20:46:27 GMT

Revision 5 posted to Article by Kim Day on 10/31/2023 8:46:27 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Checklists

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

Kim Day — Tue, 31 Oct 2023 20:35:45 GMT

Revision 4 posted to Article by Kim Day on 10/31/2023 8:35:45 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Tags: integrations, database, monitoring, Architecture

Database Operations with Slow Execution Phases

matt.cosenza — Tue, 17 Oct 2023 19:03:35 GMT

Revision 3 posted to Article by matt.cosenza on 10/17/2023 7:03:35 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Database Operations with Slow Execution Phases

matt.cosenza — Tue, 17 Oct 2023 19:02:51 GMT

Revision 2 posted to Article by matt.cosenza on 10/17/2023 7:02:51 PM

This page describes the recommended approach to database operations with slow execution phases, which is the case if:

The database is identified as the root cause for a slow interface (possibly using the Interface Performance and Debugging section as a guide)
You determined that the execute phase was the longest phase of your query execution operation
You optimized slow running queries in the database. Follow, Database Performance Best Practices if you need assistance in optimizing your database

Required Actors

Database Administrator
Network Administrator
Appian Administrator/Cloud Technical Support

Database Administrator Checklist

Turn on Trace Database Logging (Ex: SQL Profiler in SQL Server)
Database trace logging should include request received time, response sent time and database locking information

Network Administrator Checklist

Turn debugging (i.e. tcpdump) for packets which are routed from Appian to the database

Appian Administrator Checklist

Set hibernate debugging to TRACE (log4j.logger.org.hibernate.SQL=DEBUG and log4j.logger.org.hibernate.type=TRACE) in appian_log4j.properties
Turn on expression trace logging.
Ensure that the network and database administrators activated network packet debugging and database debugging respectively

Analyzing the Log Files

Collect and collate the log files from Appian, the Database and the Network Administrator into a single table like the one below

Appian Example Log File

The difference between the last BasicBinder entry and the first BasicExtractor entry represent the round trip between Appian and the database.

2015-10-10 03:17:13,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] DEBUG org.hibernate.SQL - select top 1 this_.[customerid] as y0_ from [customer] this_ where (this_.[customerid]=?)
2015-10-10 03:17:13,321 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicBinder** - binding parameter [1] as [INTEGER] - 12345
2015-10-10 03:17:57,123 [Appian Work Item - 0 - ProcessExec01 : ExpressionGroupRequest] TRACE org.hibernate.type.descriptor.sql.**BasicExtractor** - found [12345] as column [y0_]

You may need to run the trace logging during a time of low or no load if the amount of trace logging messages are unmanageable.

Example 1: Network Latency

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:33	20s Network Latency
Database Sends Response	3:17:35	2s Database Time
Router Receives Packet	3:17:35	0s Network Latency
First BasicExtractor Statement	3:17:57	22s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent during transport of the request and the response back and forth between Appian and the database.

Contact the network administrator if a majority of the time is spent on the network

Example 2: Database Bottleneck

Timing	Log Timestamp	Delta
Last BasicBinder statement	3:17:13
Router Receives Packet	3:17:13	0s Network Latency
Database Receives Query	3:17:14	2s Network Latency
Database Sends Response	3:17:55	41s Database Time
Router Receives Packet	3:17:56	0s Network Latency
First BasicExtractor Statement	3:17:57	1s Network Latency
Total Time	44s
Expression Trace Time	46s	2s Appian Overhead

Notice that a majority of the time is spent on the database.

Contact the database administrator if a majority of the time is spent on the database Review the Database Performance Best Practices to improve the query execution times

Determine which area is responsible for the majority of the execution time.

Contact the Appian Cloud team if the majority of time is spent between Appian and the server hosting the VPN connection

Database Operations with Slow Execution Phases

joel.larin — Thu, 31 Aug 2023 19:05:31 GMT

Revision 1 posted to Article by joel.larin on 8/31/2023 7:05:31 PM

temp