The SQL To Insert Dynamic Action streamlines the process of exporting SQL datasets into an INSERT SQL script. This action retrieves data dynamically from a SQL query or database table and generates a sequence of INSERT statements, which can be used to replicate the dataset in another database. It is particularly useful for database migration, data backups, or creating test data for development and testing environments. By automating the generation of INSERT scripts, this action eliminates the need for manual scripting, reduces errors, and ensures consistency when transferring data across databases.
Metadata tab
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.
This option is typically used for debugging and is not recommended in a production environment.
It can be globally disabled through the
options dialog
.
Parameters tab
Tips
The “Replace Variables” parameter is used to substitute variables within SQL statements.
When the “UseEmbeddedSQL” is set to True EmbeddedSQL is used, otherwise SQL Script/Lookup is used.
To minimize potential issues, avoid using mapped drives and opt for the UNC (Universal Naming Convention) path instead. Mapped drives can lead to problems with accessibility and permissions, especially in networked environments or automated processes. UNC paths provide a direct, reliable way to reference network resources without relying on local drive letters, ensuring better stability and consistency across different systems and users.
Selecting Script
Editing Script
Selecting Connection
Variables tab
The Variables tab defines the variables to be updated during the action’s execution.
Tip: double click on the variable name to disable/enable it
Execution log tab
The Execution log tab is populated after the action is executed. Double click on the row to view the log.