MS SQL
The following document assumes that you understand the basics of connecting to databases on Appsmith. If not, please go over them before reading further.
Microsoft SQL Server is a relational database management system developed by Microsoft that supports a wide variety of transaction processing, business intelligence, and analytics applications in corporate IT environments.
Appsmith's backend server supports TLS1.1 and TLS1.2 for connecting to endpoints.

Connection Settings

Appsmith needs the following parameters for connecting to an MsSQL database:
All required fields are marked with an asterisk (*).

Connection

  • Connection Mode:
    • Read / Write: Choosing this mode gives Appsmith both read and write permissions on the database. It allows you to execute all CRUD queries.
    • Read Only: Choosing this mode gives Appsmith read-only permission on the database. It only allows you to fetch data and prevents making any changes.
  • Host Address / Port: Fill in the database host's address and port. If you don't specify a port, Appsmith will try to connect to port 5432 by default.
  • Database Name: Fill in the name of the database that you want to connect to.

Authentication

  • Username: Fill in the username for the database user responsible for approving connection requests.
  • Password: Fill in the password required to log in with the provided username.

SSL

In this optional section, you may handle any SSL configuration required to connect to your database.
  • SSL Mode: Choose your SSL model from the dropdown.
  • Key File: Upload your SSL key file from here.
  • Certificate: Upload your SSL certificate here.
  • CA Certificate: Upload your CA certificate here.
  • PEM Certificate: Upload your PEM certificate here.
  • PEM Passphrase: Fill in your PEM passphrase here.

Querying MsSQL

You can query MsSQL databases using the standard T-SQL syntax. When you create a new query, Appsmith can provide some template SQL to help understand the basic syntax:
Appsmith can provide short SQL templates to guide your query
MsSQL queries will return an array of objects; each object represents a row, and each property in that object represents a column.
[
{ id: “1”, color: “blue” },
{ id: “1”, color: “periwinkle” },
{ id: “1”, color: “chartreuse” },
]
Lastly, you may wish to enable the "Request confirmation before running query" setting to help avoid accidentally destructive actions. You can find this option in the Settings tab of the query.
Enable this setting in your query to require user confirmation before potentially destructive actions
For a more detailed walkthrough of using Appsmith to run queries against an MsSQL database, you can also check out this blog post!

Using Prepared Statement (Beta)

Normal query execution simply string concatenates the evaluated values of the javascript bindings to produce the final query. This opens up the possibility of SQL injection by merging untrusted user input with trusted data for execution. Using a prepared statement is one strategy for mitigating this risk.
Appsmith converts the user query into a parameterized one by replacing the bindings in the query with '?'. The payload is then inserted one by one ensuring that the bindings get properly escaped and sanitized before the query is sent to the database for execution.
Follow the guide on how to use prepared statements for efficient and secured data transactions.

Using Queries in Applications

Once you have successfully run a Query, you can use it in your application to