We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello everyone,
Can we use only SQL Pool without Spark Pool, which still allow us to use SQL script to query the data?
Thanks,
Solved! Go to Solution.
Hi @LBDeveloper
Thanks for using Fabric Community.
In Microsoft Fabric, you can indeed use a SQL Pool without a Spark Pool, and still leverage SQL scripts to query your data.
When you create a SQL Pool, you can upload your data to the pool, and then use SQL scripts to query, transform, and analyze the data. The SQL Pool takes care of executing the queries, and you can retrieve the results for further analysis or visualization. In this scenario, you don't need a Spark Pool to use SQL scripts to query your data. The SQL Pool is a self-contained compute resource that can execute SQL queries independently.
Spark Pools, on the other hand, are designed for big data analytics workloads that require distributed processing, such as data engineering, data science, and machine learning tasks. If you don't need these advanced capabilities, a SQL Pool is a great choice for running SQL queries against your data.
Benefits of using a SQL Pool without a Spark Pool:
Simplified architecture: You don't need to worry about setting up and managing a Spark Pool, which can be complex and resource-intensive.
Lower costs: SQL Pools are generally more cost-effective than Spark Pools, especially for smaller-scale workloads.
Faster query performance: SQL Pools are optimized for relational queries, which can result in faster query performance compared to Spark Pools.
Easier data management: You can manage your data and schema directly within the SQL Pool, without needing to worry about Spark-specific data structures.
When to use a Spark Pool If you need to perform advanced analytics, machine learning, or data engineering tasks, a Spark Pool is a better choice. Spark Pools offer:
Distributed processing: Spark Pools can handle large-scale data processing tasks by distributing the workload across multiple nodes.
Advanced analytics: Spark Pools support advanced analytics libraries, such as MLlib and GraphX, which enable machine learning, graph processing, and other advanced analytics capabilities.
Big data support: Spark Pools can handle massive datasets and perform data engineering tasks, such as data ingestion, processing, and transformation.
Hope this helps.
Hi @LBDeveloper
Thanks for using Fabric Community.
In Microsoft Fabric, you can indeed use a SQL Pool without a Spark Pool, and still leverage SQL scripts to query your data.
When you create a SQL Pool, you can upload your data to the pool, and then use SQL scripts to query, transform, and analyze the data. The SQL Pool takes care of executing the queries, and you can retrieve the results for further analysis or visualization. In this scenario, you don't need a Spark Pool to use SQL scripts to query your data. The SQL Pool is a self-contained compute resource that can execute SQL queries independently.
Spark Pools, on the other hand, are designed for big data analytics workloads that require distributed processing, such as data engineering, data science, and machine learning tasks. If you don't need these advanced capabilities, a SQL Pool is a great choice for running SQL queries against your data.
Benefits of using a SQL Pool without a Spark Pool:
Simplified architecture: You don't need to worry about setting up and managing a Spark Pool, which can be complex and resource-intensive.
Lower costs: SQL Pools are generally more cost-effective than Spark Pools, especially for smaller-scale workloads.
Faster query performance: SQL Pools are optimized for relational queries, which can result in faster query performance compared to Spark Pools.
Easier data management: You can manage your data and schema directly within the SQL Pool, without needing to worry about Spark-specific data structures.
When to use a Spark Pool If you need to perform advanced analytics, machine learning, or data engineering tasks, a Spark Pool is a better choice. Spark Pools offer:
Distributed processing: Spark Pools can handle large-scale data processing tasks by distributing the workload across multiple nodes.
Advanced analytics: Spark Pools support advanced analytics libraries, such as MLlib and GraphX, which enable machine learning, graph processing, and other advanced analytics capabilities.
Big data support: Spark Pools can handle massive datasets and perform data engineering tasks, such as data ingestion, processing, and transformation.
Hope this helps.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 16 | |
| 8 | |
| 8 | |
| 4 | |
| 4 |
| User | Count |
|---|---|
| 35 | |
| 24 | |
| 13 | |
| 11 | |
| 11 |