Microsoft Fabric: A Comprehensive Data Management Solution Microsoft Fabric presents a unified, robust platform designed to optimize data management, enhance AI model development, and empower users across an organization. It focuses on integrating data seamlessly, ensuring governance and security, and providing AI capabilities. Microsoft Fabric is presented as an all-encompassing data management solution, providing organizations with tools for efficient data integration,…
N/A
Amazon Redshift
Score 9.0 out of 10
N/A
Amazon Redshift is a hosted data warehouse solution, from Amazon Web Services.
$0.24
per GB per month
Pricing
Microsoft Fabric
Amazon Redshift
Editions & Modules
No answers on this topic
Redshift Managed Storage
$0.24
per GB per month
Current Generation
$0.25 - $13.04
per hour
Previous Generation
$0.25 - $4.08
per hour
Redshift Spectrum
$5.00
per terabyte of data scanned
Offerings
Pricing Offerings
Microsoft Fabric
Amazon Redshift
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Use Microsoft Fabric by purchasing Fabric Capacity, a billing unit that enables each Fabric experience. Pay for every data tool in one transparent, simplified pricing model and save time for other business needs.
Fabric Capacity is priced uniquely across regions.
I would highly recommend Microsoft Fabric, especially for medium to large enterprises aiming to build a robust, scalable, and secure data analytics platform. It effectively unifies various data workloads, streamlining data integration, engineering, and particularly enhancing our ability to create and share reliable Power BI dashboards. The deep integration with Azure AD for features like Row-Level Security is a significant advantage for data governance.
If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for)
Redshift is fully managed. Small teams do not have the resources to maintain a cluster. CloudWatch metrics are provided out-of-the-box, and it is easy to configure alarms.
Redshift's console allows you to easily inspect and manage queries, and manage the performance of the cluster.
Redshift is ubiquitous; many products (e.g., ETL services) integrate with it out-of-the-box.
Writing .csvs to S3 and querying them through Redshift Spectrum is convenient.
It could benefit from adding data integrity and programming tools common to other database management systems.
Amazon Redshift is based on PostgreSQL 8.0.2. That version of PostgreSQL was released in December 2006. While PostgreSQL was much improved since then, the new features were not implemented in Redshift. Many basic features are missing from it.
Primary keys can be declared but not enforced. Referential integrity (foreign keys) can be declared but not enforced. UNIQUE and CHECK constraints are not supported and cannot be declared.
IDENTITY can be declared on a column, and Redshift will put unique values into it. However: IDENTITY values in the newly inserted rows won’t be incremental or sequential. To implement a sequential number, you need to write your own custom code.
There are no stored procedures in Redshift. We are writing SQL script files, and then parsing and running them one statement at a time from a Python program. This also enabled us to implement execution-time error logging.
In SQL scripts, to check for the row count of affected rows, a complicated join query against some system tables or views has to be executed.
Data Control Language (DCL) does not exist. No statements like IF, WHILE, DO, RAISERROR, etc.
On performance of views… Views do not “pass-through” a query parameter which is a potential problem for performance.
When selecting against a view with the WHERE clause outside of the view, the inner query of the view will be executed first without consideration for the WHERE clause, and only then the WHERE clause will be applied.
Certain clauses of SQL work many times faster than other clauses. So be careful and test your statements for performance earlier rather than later, especially if working with a large data set.
There was a situation when DELETE FROM JOIN was unacceptably slow. Replacing JOIN with the USING clause made DELETE instantaneous.
I've rated Microsoft Fabric's overall usability as a 4, primarily due to its extensive and multifaceted feature set, which can make it challenging to navigate and determine the optimal functionality for a given task.While the breadth of capabilities is a core strength for large enterprises, it often leads to a sense of being "lost" or overwhelmed for teams like ours that do not have highly formalized roles or dedicated specialists for each Fabric "experience" (e.g., Data Engineering, Data Warehousing, Data Science).
Overall it serves all our aspects of data management like data cleaning, data manipulation, and data reporting on the cloud platform. We can create stored procedures and triggers in it very easily as all the options are self suggested in it. We can easily attach the results of ARS to the other tools as well for drawing the statistical results.
The support was great and helped us in a timely fashion. We did use a lot of online forums as well, but the official documentation was an ongoing one, and it did take more time for us to look through it. We would have probably chosen a competitor product had it not been for the great support
Microsoft Fabric integrates data ingestion, engineering, warehousing, and Power BI visualization into one cohesive environment. This "one-stop shop" approach dramatically reduces complexity, minimizes operational overhead, and eliminates the need to integrate disparate tools and manage data across multiple systems. It provides superior scalability for large datasets, supports open data formats, and offers a much broader suite of data engineering and data science capabilities.In essence, Fabric's integrated ecosystem and streamlined operational management were key differentiators, providing a more cohesive, scalable, and efficient solution for our evolving data strategy than combining specialized tools.
We evaluated [Amazon] Redshift vs BigQuery vs Amazon EMR, back in 2014. Back then BigQuery cost was slightly higher than that of [Amazon] Redshift price structure. Amazon EMR, needs lots more management (Admin tasks) and EMR is designed to be ephemeral and not designed to be a data store. [Amazon] Redshift was ideal with the price structure, performance and ROI[.]
