Check Connection Dynamic Action

About

The “Check Connection” package action is a useful tool designed to quickly and easily verify whether a database server is up and running. This action allows users to determine if the database server is available and ready to accept connections without needing to run complex queries or scripts.

By simply executing the “Check Connection” action, the system attempts to establish a connection with the target database server. If the connection is successful, it indicates that the server is operational and responsive. On the other hand, if the connection fails, it can signify potential issues such as the server being offline, network problems, or incorrect connection settings.

Key advantages of the “Check Connection” package action include:

  1. Real-Time Server Status: It provides an immediate indication of whether the database server is currently accessible, enabling users to quickly troubleshoot connectivity issues.
  2. Error Diagnosis: In the case of connection failure, the action typically returns error messages or codes that can help identify the underlying cause, such as invalid credentials, network timeouts, or server misconfigurations.
  3. Automation Integration: This action can be integrated into automated workflows, such as deployment pipelines or scheduled maintenance tasks, to periodically check database connectivity. If the server goes down, alerts can be triggered, allowing administrators to respond promptly.
  4. Pre-Execution Validation: Before performing critical operations like data migration, backups, or batch processing, the “Check Connection” action ensures that the server is ready to handle the requests, reducing the risk of failures or incomplete tasks.
  5. Simplicity and Convenience: Unlike more detailed diagnostic tools, the “Check Connection” action is designed to be quick and straightforward, offering a convenient way to test basic server availability without the need for deep technical expertise.

Metadata tab

Check Connection Action - Metadata tab
 

  1. The Write Variables option ensures that the “Package Action” logs the variable values into the “Action vars before log file” before the action is executed and logs the updated variable values into the “Action vars after log file” after the action completes.
  2. This option is typically used for debugging and is not recommended in a production environment.
  3. It can be globally disabled through the options dialog .

Parameters tab

Check Connection Action - Parameters tab

Selecting Connection

Check Connection Action - Editing Check Connection Connection Parameter

Variables tab

The Variables tab defines which variables are updated during the execution of the action.

Check Connection Action - Variables tab

Execution log tab

The Execution Log tab is populated after the action has been executed. Double-click a row to view the detailed execution log.

Check Connection Action - Execution log tab

Calculated parameters example

Pascal

Check Connection Action - Calculated Parameter example - Pascal
  Script

begin
 if DayOfWeek(Now)=3 then
    begin
     Result:=1917;
    end
 else
    begin
     Result:=1968;
    end;
end;

Python

Check Connection Action - Calculated Parameter example - Python
  Script

import datetime;
if datetime.datetime.today().weekday()==0:
   Result.Value=3917
else:
   Result.Value=3918
  1. Sql Script Action
  2. Sql Data Check Action
  3. Check Connection Action

For more technologies supported by our ETL Software see Advanced ETL Processor Versions

Confused? Ask question on our ETL Forum

Posted on December 31, 2024 • 3 min read • 483 words
www.etl-tools.com About Support Pricing Cookies Policy Term Of Use Privacy Policy License