Databases

SQL Server
integration

Build internal apps on Microsoft SQL Server and Azure SQL data with ToolJet.

Start building Read the setup guide

Configure your connection, create queries, and build the interface your team needs. Try a sample prompt

Connector capabilities

What can ToolJet do with SQL Server?

Create queries for the operations your app needs, then connect their inputs and results to the interface.

Run SQL queries
List and create rows
Update and delete rows
Bulk insert and upsert

Operations and configuration can vary by connector version. Check the full SQL Server guide.

An app you could build

Order operations across SQL Server and other systems

Build an order workspace that reads sales records from SQL Server, looks up inventory in PostgreSQL, and requests shipment status from a REST API. Configure each connection and query separately, match records by order or product ID, and test missing records and partial failures before enabling write actions.

Try this prompt

I have sales records in SQL Server with territory, representative, date, and amount columns. Build a sales dashboard with territory and date filters. Show revenue summaries and a table where I can inspect individual sales records.

Start with this prompt in ToolJet. Sign in or create an account, then connect your data source and replace the example names and fields with yours.

Review the generated app, configure permissions, and test its queries before sharing it with your team.

Explore app templates

Connect SQL Server

Start with the connection.

Before you begin

A reachable SQL Server or Azure SQL database and a database identity with the required permissions. The setup guide documents SQL authentication and Azure AD service-principal authentication. Check the options supported by your installed ToolJet version and configure network access before testing the connection.

Add the data source
Open Data Sources in your ToolJet workspace. Select SQL Server and enter the required connection details.
Configure and test a query
Choose an operation and supply its inputs. Start with a read operation where available; test writes with non-production data.
Build the interface
Bind query results to components and connect actions to app events. Verify permissions and error handling before rollout.

SQL Server setup guide

Before production

Use a least-privilege database identity and parameterized queries. App login and database authentication are separate: do not assume a shared connection inherits each user's database permissions. Enforce record access in server-side queries, database policies or APIs, and test denied access as well as successful operations.

Review plans and deployment options

Frequently asked questions

What can I do with the SQL Server integration?

Build internal apps on Microsoft SQL Server and Azure SQL data with ToolJet. Supported capabilities: Run SQL queries; List and create rows; Update and delete rows; Bulk insert and upsert.

What do I need to connect SQL Server to ToolJet?

What should I check before using SQL Server in production?

Can I automate tasks with SQL Server?

Connect SQL Server queries to app events such as button clicks and form submissions. ToolJet Workflows and Agent Builder can orchestrate supported connectors on Self-hosted deployments; those products are not available on ToolJet Cloud. Check the connector and deployment requirements for your use case.

Can a ToolJet app combine Microsoft SQL Server with PostgreSQL and REST APIs?

Yes. Configure SQL Server or Azure SQL, PostgreSQL and REST API data sources in the same ToolJet app, then bind their query results to tables, forms and charts. Each source retains its own credentials and access requirements. Plan how records match across systems and how the app handles unavailable services; connecting sources does not automatically synchronize their data or create a cross-database transaction.

What should we test when evaluating ToolJet as a Power Apps alternative for mixed data?

Choose one representative process spanning a Microsoft database and a non-Microsoft system. Test reads, approved writes, network access, authentication and record-level authorization for every source. Separately inventory any Power Fx formulas, Dataverse rules and Power Automate flows: a SQL Server connector does not import or replace those application behaviors. Rebuild and validate the required behavior before migration, and confirm deployment and plan requirements.

Keep exploring

Related integrations

Browse all integrations

PostgreSQL

MySQL Oracle Database IBM Db2

MariaDB SAP HANA

Put SQL Server to work
in your next internal app.

Connect your data, build an interface, and give your team a focused workspace.

Start building Book a demo

Connector information reviewed 2026-11-01. Source: ToolJet documentation.