Microsoft SQL Server
Connect Superblocks to Microsoft SQL to build apps with read and write access to a Microsoft SQL database:
- Read data from a database and utilize it in API steps or UI components
- Save information retrieved by other API steps or UI components by writing data to a database
Setting up Microsoft SQL
1. Add integration
Select Microsoft SQL from the integrations page.
2. Configure settings
Fill out the form with the following settings:
|Name||Name that will be displayed to users when selecting this integration in Superblocks|
|Host||Hostname or IP address to connect to|
|Port||Port to use when connecting to Microsoft SQL|
|Database Name||Name of database to connect to|
|Database Username||Username to use to connect|
|Database Password||Password for database username|
|Enable SSL||Connect via SSL if selected|
3. Test and save
Click Test Connection to check that Superblocks can connect to the data source.
After connecting successfully, click Create to save the integration.
4. Set profiles
Optionally, configure different profiles for separate development environments.
Creating Microsoft SQL steps
Connect to your Microsoft SQL integration from Superblocks by creating steps in Application APIs, Workflows, and Scheduled Jobs. You can configure a Superblocks Microsoft SQL integration with read only, read/write, or write only users. You can then configure a Superblocks Microsoft SQL step to read from a database, as well as modify/delete data. To get started, enter your SQL query into the text area of the Microsoft SQL step. Then click "Run" to see the Result and Executed SQL statement below.
Create an admin dashboard that reads from Microsoft SQL and other sources. Mix in APIs to allow support agents to refund orders, update shipping statuses, or transform large datasets in a single UI.
Enrich customer order data within Microsoft SQL with shipping data from Snowflake or other datastores.
Send out a daily report via email of new customer bookings.
Check out our guide on common errors across database integrations, in addition to common Microsoft SQL Server connection issues. If you are encountering an error that you don't see in the guide, or the provided steps are insufficient to resolve the error, please contact us at email@example.com.