SQL execution
Run SELECT, INSERT, update, or other approved SQL statements as part of a workflow.
MS SQL Database component
Use MS SQL Database when workflow automation needs to read or write SQL Server data inside the customer environment.
Query and update Microsoft SQL Server data from controlled integration flows.
What this component unlocks
The docs describe the Microsoft SQL Database component as supporting SQL statements, query testing, connection testing, and JSON or table output views. Builders select stored database credentials, manage credentials, and use Test Connection before running SQL. The SQL editor can be resized vertically, Test Query runs valid SQL from the editor, and output can be reviewed as JSON or a table with clear success or error feedback.
Run SELECT, INSERT, update, or other approved SQL statements as part of a workflow.
Verify credential and network access before saving or executing a database step.
Review query results as JSON or a table while configuring the component.
Use cases
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use MS SQL Database as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Configuration surface
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Use Test Connection before query execution.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Review query errors carefully.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Use least-privilege credentials and avoid unbounded production queries.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Start with an event, use MS SQL Database, then route the result to CRM, ticketing, or a customer-owned system.
Add validation, human approval, and logging around the component before downstream actions execute.
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.