Azure SQL Server

This section covers the integration with Azure SQL Server.

The Azure SQL Server Database config is the way Ardent gains the ability to work with data in your Azure SQL Server Database. It is designed to take in basic auth credentials and use that to automatically understand the data within your database and tables so you can perform operations on it.

Usage

To use the Azure SQL Server integration with Ardent, you need to provide the necessary configuration details. Here's an example of how to set up the Azure SQL Server config:

  1. Find the Configs Section: Go to the configs section in the app

    Find the configs section

  2. Add a Config: Click Add New Config

Add New Config

  1. Select Config: Select the Azure SQL Server config

Add New Config

  1. Enter Values and Save Config: Configs will not save until you hit "save". Enter the necessary information for your config and hit Save
    • Server: Your Azure SQL Server address (e.g., yourserver.database.windows.net)
    • Username: Your Azure SQL Server admin username
    • Password: Your Azure SQL Server password
    • Database: Your database name
    • Tables: Add any tables you want to work with

Azure SQL Setup

Connection Details

The Azure SQL Server config requires:

  • Server: The address of your Azure SQL Server
  • Username: Your Azure SQL Server admin username
  • Password: Your Azure SQL Server password
  • Database: The name of your database
  • Tables: The specific tables you want to work with

You can add multiple tables to a single configuration by using the "Add Table" button.

Note on Connection Configurations

Azure SQL Server requires:

  • A running Azure SQL Server instance
  • Valid authentication credentials
  • Proper database permissions
  • Valid table names that exist in your database
  • Appropriate read/write permissions for the authenticated user
  • Important: Make sure your Azure SQL Server firewall rules allow connections from external IPs

For more information about Azure SQL Server connection configuration, please refer to the Azure SQL documentation.