Understanding the Data Pipelne

  • Updated on Oct 8, 2025
  • Published on Oct 8, 2025
  • 5 minute(s) read
Prev Next

🧠 Purpose

Aspire’s Data Pipeline provides a seamless way to access key data from your Aspire system. Each night, select data tables are securely pushed to an external database server managed by your team. This enables you to leverage your data for reporting, analytics, and other business needs.

Let’s explore how the Data Pipeline works and what it means for your organization.

Choosing Between the Data Pipeline and API

Aspire offers two key methods for accessing and integrating data: the Data Pipeline and the REST API. Each serves different needs depending on how you plan to use your data.

When to Use the Data Pipeline

The Data Pipeline is ideal for organizations looking to build in-house analytics and maintain historical data in a centralized location.

  • Custom Analytics – Clients can use tools like Microsoft Power BI or Tableau to analyze data.
  • Historical Data Access – Since the pipeline syncs data nightly, there will be a lag between updates.
  • Stable, Centralized Repository – Stores large volumes of historical data for trend analysis and reporting.
  • Technical Expertise Required – Users need experience with databases and large data sets to maximize its value.

When to Use the REST API

The REST API is designed for real-time data access and seamless integration with third-party applications.

  • Third-Party Integrations – Connect Aspire with other software, such as CRM or marketing platforms.
  • Real-Time Data Access – Retrieve and update data instantly, without waiting for nightly syncs.
  • Event-Driven Automation – For example, automatically create a property and contact in Aspire when a lead form is submitted on a website.
  • No Database Knowledge Required – Returns structured data without requiring expertise in Aspire’s database relationships.
  • Flexible Data Retrieval – View only updated records since a given date/time or make periodic data calls throughout the day.

Key Differences

  • The Data Pipeline is a one-way nightly sync of raw data for analytics and reporting.
  • The REST API enables real-time, bidirectional data exchange for automation and integrations.

If you need historical data for reporting, the Data Pipeline is the right choice. If you require real-time data or integrations, the REST API is the better fit.

📌Note: For more information on the REST API, click here!

Client Responsibilities

To use the Aspire Data Pipeline, clients must set up and manage their own database environment. This includes configuring access and security settings to ensure a successful connection.

Setup Requirements

  • Azure SQL Database – The database server must be created and configured within Microsoft Azure.
  • Access & Security – Credentials and firewall settings must be properly configured to allow incoming connections from Aspire.
  • Database Sizing – Aspire will provide guidance on the appropriate database size based on your data needs.

Ensuring these requirements are met will allow for a smooth data transfer and optimal performance!

What Data is Available?

When an Aspire client selects the Data Pipeline, they receive a schema document detailing the tables, columns, and data types in the Aspire database source. This is typically provided as a Google Sheet or Excel Spreadsheet, making it easy to review for those unfamiliar with SQL.

For clients who prefer alternative formats, Aspire offers additional schema options:

  • SQL Script – A script that creates the schema in SQL. Ideal for clients comfortable with SQL who prefer a direct database implementation.
  • Data Definition Language (DDL) File – Defines the schema structure for integration with tools that require DDL files.
  • JSON Schema – Describes the database structure in JSON format, useful for integrating with JSON-based applications or systems.

Clients can choose the schema format that best fits their workflow and technical expertise.

What IP Address is Used for Incoming Data?

The data pipeline will follow Azure Integration Runtime for IP Addresses. Click here for more information.

Data Pipeline Pricing & Billing

Access to the Aspire Data Pipeline is available for an additional cost of $1,000 per month, which will be added to your regular invoice.

How to Get Started

  • Contact your Aspire Account Executive to request a contract addendum.
  • Once signed, billing begins in the third month following the signature date to allow time for database setup.

Example Billing Timeline

  • Contract Signed: February 15th
  • Billing Starts: May invoice

📌Note: This delayed billing ensures you have ample time to establish your database connection before charges begin.

Support & Assistance

Clients are responsible for building and maintaining their database environment. However, if technical questions arise, support is available.

How to Get Help

  • Clients can submit support tickets through AspireCare for technical assistance.
  • AspireCare can help address questions related to data access, schema details, and connection issues.

For ongoing database management and optimization, clients should ensure they have the necessary technical expertise.

Configuring an Azure SQL Database for Aspire Data Pipeline

To receive data from the Aspire Data Pipeline, clients must configure an Azure SQL Database with the appropriate settings and performance tier.

  1. Set Up an Azure SQL Database
    • Create an Azure SQL Database using your preferred configuration options.
    • Refer to Microsoft’s Azure SQL Database Overview for detailed setup guidance.
  2. Select the Right Service Tier
    • A recommended starting point for the sink database (destination) is the Premium P4 tier, which includes:
      1. 500 DTUs (Database Transaction Units)
      2. 1TB maximum database size
    • If higher performance is needed, consider a higher-tier plan based on your specific workload.
    • Testing and benchmarking are recommended to determine the optimal configuration for your use case.
  3. Supported Data Stores & Formats

Other Azure Sinks/Destinations:

  • Azure Blob Storage
  • Azure AI Search inde
  • Azure Cosmos DB for NoSQL
  • Azure Cosmos DB for MongoDB
  • Azure Data Explorer
  • Azure Data Lake Storage Gen1
  • Azure Data Lake Storage Gen2
  • Azure Database for MySQL
  • Azure Database for PostgresSQL
  • Azure Databricks Delta Lake
  • Azure Files
  • Azure SQL Managed Instance
  • Azure Synapse Analytics
  • Azure Table Storage

Other Compatible Database Sinks/Destinations:

  • Informix
  • Microsoft Access
  • Oracle
  • Snowflake
  • SQL Server
  • MongoDB
  • MongoDB Atlas

File System Compatible Sinks/Destinations:

  • Standard file system formats
  • SFTP

Generic Protocol

  • ODBC
  • REST

Services and apps

  • Dataverse
  • Dynamics 365
  • Dynamics CRM
  • Salesforce
  • Salesforce Service Cloud
  • SAP Cloud for Customer (C4C)

Aspire Azure resources are located in the WestUS region. Therefore, your server should be configured to allow traffic from the IP addresses listed for the Azure Integration runtime in the West US Azure region. You can get an IP range list of service tags from the service tags IP range download link.

Obtain and provide to Aspire the following information:

  • Fully Qualified Domain Name of the host server
  • Type of destination if not an Azure SQL Database
  • Database Name
  • User Access Credentials
  • Preferred schedule (time of day in Central Time zone) for data refresh

Aspire’s Data Delivery & Analytics team will provide setup configuration and will work closely with you to ensure implementation of the pipeline is successful.

⚠️ Post-Implementation Support will be coordinated through AspireCare. For more information on submitting a ticket to AspireCare, click here.