Trusted by data-driven companies
Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes
Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say
"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"
“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”
“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
Azure Table Storage is a schemaless NoSQL datastore that stores data as entities with key-value pairs. Each entity has:
- Partition Key: Groups related entities for efficient querying.
- Row Key: Uniquely identifies an entity within a partition.
- Timestamp: A system property indicating the last modification time.
MSSQL, on the other hand, uses a relational schema with tables, rows, columns, and constraints. You need to map Azure Table Storage entities into MSSQL tables with appropriate schema design.
Azure Table Storage
- Verify that you have access to the Azure Storage account containing the table data.
- Retrieve the table endpoint URL and access credentials (Account Key or Shared Access Signature).
- Identify the table(s) you wish to migrate and analyze their structure.
MSSQL Database
- Set up your MSSQL instance (on-premises or cloud-based).
- Create a database and define the schema based on how you plan to structure the data from Azure Table Storage.
- Ensure you have administrative access to execute bulk operations.
You can use Azure SDKs or REST APIs to extract data programmatically:
Access Azure Table Storage:
- Use Azure SDKs for .NET, Python, or JavaScript, which provide libraries for interacting with Azure Table Storage.
- Alternatively, use REST APIs with OData queries to fetch entities directly.
Query Data:
- Retrieve entities using partition keys and row keys for efficient filtering.
- Use batch queries if dealing with large datasets.
Export Data:
Write the extracted data into a structured format like CSV, JSON, or XML for easier processing in MSSQL.
Since Azure Table Storage is schemaless, you need to transform the data into a relational format suitable for MSSQL:
Map Properties:
- Define how each property in an entity corresponds to columns in your MSSQL table.
- Include primary keys (partition key + row key) as unique identifiers in MSSQL.
Handle Null Values:
Ensure that properties missing in some entities are mapped as nullable columns in MSSQL.
Normalize Data:
If necessary, split denormalized data into multiple tables for relational design.
Option 1: Using Bulk Insert
- Save transformed data in CSV format.
- Use MSSQL's BULK INSERT command or SQL Server Management Studio (SSMS) Import Wizard to load data into tables.
Option 2: Using Custom Scripts
- Write scripts using programming languages like Python or .NET.
- Use libraries such as pyodbc (Python) or ADO.NET (.NET) to connect to MSSQL and insert data programmatically.
Option 3: Using Stored Procedures
- Create stored procedures in MSSQL for batch insertion of rows.
- Call these procedures from your script after extracting and transforming data.
After loading the data into MSSQL:
- Compare row counts between Azure Table Storage and MSSQL tables.
- Verify that all properties have been correctly mapped and populated.
- Check constraints, indexes, and relationships in MSSQL tables.
- Run queries on both systems to ensure data consistency.
- Index frequently queried columns in MSSQL for better performance.
- Partition large tables if necessary to improve query efficiency.
- Monitor database performance metrics after migration.
- Remove temporary files (e.g., CSV or JSON files used during transformation).
- Revoke unnecessary access permissions on Azure Table Storage and MSSQL databases.
- Document the migration process for future reference.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Azure Table storage, which is a service that stores non-relational structured data in the cloud and it is well known as structured NoSQL data. Azure Table storage is a service that stores structured NoSQL data in the cloud, providing a key/attribute store with a schema less design. Azure Table storage is a very popular service used to store structured NoSQL data in the cloud, providing a Key/attribute store. One can use it to store large amounts of structured, non-relational data.
Azure Table Storage's API gives access to structured data in the form of tables. The tables are composed of rows and columns, and each row represents an entity. The API provides access to the following types of data:
1. Partition Key: A partition key is a property that is used to partition the data in a table. It is used to group related entities together.
2. Row Key: A row key is a unique identifier for an entity within a partition. It is used to retrieve a specific entity from the table.
3. Properties: Properties are the columns in a table. They represent the attributes of an entity and can be of different data types such as string, integer, boolean, etc.
4. Timestamp: The timestamp is a system-generated property that represents the time when an entity was last modified.
5. ETag: The ETag is a system-generated property that represents the version of an entity. It is used to implement optimistic concurrency control.
6. Query results: The API allows querying of the data in a table based on specific criteria. The query results can be filtered, sorted, and projected to retrieve only the required data.
Overall, Azure Table Storage's API provides access to structured data that can be used for various purposes such as storing configuration data, logging, and session state management.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey:
