Add Dataset from Azure Synapse
Overview
The Azure Synapse Dataset allows you to expose a specific table from your connected Azure Synapse workspace as a structured Dataset in Sourcesible. Once configured, the Dataset can be used across Audiences, Computed Fields, and Dataset Models. Azure Synapse follows a 3-step wizard using schema-based table organization, with native type auto-detection for all columns. Before creating a Dataset, ensure you have an Azure Synapse Source already connected under Data Sources.
Creating a Dataset from Azure Synapse
Step 1 — Open the Dataset Page
- In the left navigation, click Datasets.
- Click Add Dataset in the top-right corner.
Step 2 — Choose a Data Source
- On the Choose Data Source screen, select the radio button next to Azure Synapse.
- Click Next.
Step 3 — Choose Method (Step 1 of 3)
Select how you want to define your dataset:
| Method | Description | Best For |
|---|---|---|
| Table Selector | Browse and select a table directly from your connected Azure Synapse workspace. Requires a user with read and write permissions. | Quick setup when you want the full table with no transformation |
| SQL | Write a custom query using the online SQL editor. | Custom datasets, filtered views, joins, or aggregations |
Step 4 — Choose an Azure Synapse Table (Step 2 of 3)
The Choose a Azure Synapse Table screen appears. Sourcesible fetches the list of schemas and tables from your connected workspace.
The table list may take a few seconds to load while Sourcesible connects to your Azure Synapse workspace. A loading spinner is displayed during this time. Do not navigate away until the list appears.
- Wait for the table list to finish loading.
- Tables are grouped under their parent schema (e.g., demo_vinns, oak_edu). Select the radio button next to the table you want to use. For example:
- demo_vinns → users
- oak_edu → courses, payments, student_activity_attributes, students
- Use the Search field to filter tables by name if needed.
- Click Confirm.
Step 5 — Set Up Dataset (Step 3 of 3)
The wizard advances to Set up Dataset.
Dataset Identity
- In the Dataset Name field, enter a name to identify this dataset in Sourcesible (maximum 50 characters). You can update this at any time under Settings.
- Optionally, enter a Dataset Description (maximum 50 characters).
The Dataset Name field is required. If you attempt to click Save without entering a name, the save action will not complete. Always fill in the Dataset Name before proceeding.
Source Reference (Read-only)
The following fields are auto-populated from your table selection and cannot be edited here:
- Schema Name from Azure Synapse schema — displays the schema name (e.g., oak_edu)
- Table Name from Azure Synapse Table — displays the selected table name (e.g., students)
Data Settings
The Data Settings section lists all fields detected from your selected table along with their native Azure Synapse data types (e.g., NVARCHAR, DATE). For each field, configure the following:
| Column | Description |
|---|---|
| Show In Filter | Makes this field available as a filter criterion in Audience and segmentation tools. Click the header checkbox to toggle all fields at once. |
| PII | Marks this field as Personally Identifiable Information. PII fields are displayed as masked in the data preview. |
| Exclude from Personalization | Prevents this field from being used in personalization or activation contexts. |
- Configure the Show In Filter, PII, and Exclude from Personalization checkboxes for each field as required.
- Click Preview to validate that Sourcesible can read records from the table. A preview of up to 10 rows renders inline below Data Settings.
- Review the preview data to confirm columns and values look correct.
- Click Save.
The note at the bottom of the preview reads: "For data privacy, your selected PII fields will be displayed as masked."
Test Your Connection (Preview)
When you click Preview, Sourcesible queries the first 10 records from your selected Azure Synapse table and renders them inline. The following are validated during preview:
- Sourcesible can connect to Azure Synapse using the stored credentials
- The selected schema and table exist and are accessible by the configured service principal or SQL user
- The field schema matches the columns listed in Data Settings
- PII-flagged fields render as masked values in the preview output
If the preview returns no records or an error, do not click Save. Verify that the service principal or SQL user has SELECT permission on the selected table before retrying.
Next Steps
Once your Azure Synapse Dataset is saved, you can:
- Create a Dataset Model — Join multiple Datasets together or define relationships for unified customer profiles.
- Build Computed Fields — Derive new attributes from Azure Synapse table fields.
- Define Audiences — Use fields marked Show In Filter as segmentation conditions.
- Configure Single View of Customer — Map Dataset fields to identity resolution and profile unification.
Tips and Troubleshooting
Save Button Does Not Complete — Dataset Name Missing
Symptom: Clicking Save appears to do nothing or the button flashes but the dataset is not created.
Cause: The Dataset Name field is required. Sourcesible will not save the dataset without a valid name entered.
Fix: Scroll up to the top of the Set up Dataset form, enter a name in the Dataset Name field (maximum 50 characters), then click Save again.
Table List Does Not Load or Takes a Long Time
Symptom: After reaching the Choose a Azure Synapse Table step, the loading spinner shows for more than 30 seconds or no tables appear.
Cause: Azure Synapse connection latency or the service principal lacking permission to enumerate schemas and tables.
Fix: Verify the service principal has the db_datareader role in the Synapse dedicated SQL pool or serverless SQL pool. Then check that the firewall rules allow Sourcesible's IP range to access the Synapse endpoint. Navigate Back and retry once permissions are confirmed.
No Tables Appear Under a Schema
Symptom: A schema group header is visible (e.g., oak_edu) but no tables are listed beneath it.
Cause: The database user does not have SELECT permission on any tables within that schema.
Fix: Grant the required permissions in Azure Synapse:
GRANT SELECT ON SCHEMA::oak_edu TO sourcesible_user;To grant access to all existing tables in the schema and future tables, use a database role:
EXEC sp_addrolemember 'db_datareader', 'sourcesible_user';Preview Shows null Values for Some Fields
Symptom: The preview table renders correctly but some fields (e.g., phone, location) show null for certain rows.
Cause: The underlying data in Azure Synapse contains NULL values in those columns. This is not an error — it accurately reflects the data as it exists in the source table.
Fix: No action is required in Sourcesible. If unexpected null values are present, verify and clean the data at the source in Azure Synapse before re-running the preview.