Azure Service Bus
Azure Service Bus is a cloud messaging service.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | check | |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | check | |
| Authorization via API | check |
Setup guide
Follow our step-by-step Azure Service Bus setup guide to connect Azure Service Bus with your destination using Fivetran connectors.
Schema information
IMPORTANT: You can choose which topics to sync on the Schema tab in your Fivetran dashboard.
For each topic in Azure Service Bus, we create one table in your destination.
For each table, we create the following columns as per the received message:
message_id(Primary Key)sequence_numenqueued_sequence_numbersession_idcontent_typeenqueued_timecorrelation_iddead_letter_error_descriptiondead_letter_reasondead_letter_sourceapplication_properties
If you sync JSON messages, Fivetran delivers your data in either packed or unpacked format. We do the following:
For packed messages, we sync the data into the
valuecolumn.Unpacked messages must be in JSON format. For all the first-level JSON elements, we create a separate column with the
value_<element_name>name format.
Sync note
When we sync messages from Azure Service Bus, we do not delete them. We set the MessageTimeToLive property value to 14 days. As a message remains in the queue for 14 days, the message count value in the subscription reflects the total number of messages in the subscription and not the number of messages we are yet to sync.
We don't read all the messages in each sync. We use message peeking and sync only the messages we haven't synced before.