I need to create a Dataflow within the PBI reporting service that connects to a view/Table built-in Azure Databricks. Is it possible?
Can I create a data model or join tables with Power BI Service? If yes, then in which license, pro or premium?
How do I create a hyperscale PostgreSQL DB from the Azure CLI?
Please note, I am not asking about Arc-enabled Kubernetes clusters.
The current documentation is for Portal only.
Is there a way to do this from the Azure CLI?
Furkan is here from Microsoft (PostgreSQL Hyperscale Citus team),
We currently do not support the Azure CLI based provisioning. However, we have rest APIs in private preview. You can see the API description here https://github.com/Azure/azure-rest-api-specs/tree/main/specification/postgresqlhsc/resource-manager
Are there any tools for database administration that can be deployed in AWS Lambda? My usecase is i've aurora serverless running inside a vpc and I want an AWS Lambda function to be able to visualize, clear and delete datas so developers do not need to get inside bastion hosts everytime they need to clear a row.
There is Data API for Aurora Serverless which allows you to use regular AWS SDK (e.g. boto3) to query your databases in Aurora Serverless.
Could someone explain the difference between SQL Server 2019 BDC vs Azure Synapse Analytics other than OLAP & OLTP differences? Why would one use Analytics over SQL Server 2019 BDC?
Azure Synapse Analytics is a Cloud based DWH with DataLake, ADF & PowerBI designers tightly integrated. it is a PaaS offering and it is not available on-prem. The DWH engine is MPP with limited polybase support (DataLake).
it also allows ypu to provision Apache Spark if needed.
SQLServer 2019 Big Data Cluster is a IaaS platform based on Kubernetes. it can be implemented on-prem on VMs or on OpenShift or on AKS Any cloud for that matter).
Its Data Virtualization support is very good with support for ODBC data sources and a Data Pool to support Data Virtualization- Implemented via Polybase.
Apache Spark makes up the Big Data compute.
Though it is not a MPP like Synapse, because of Pods in Kubernetes, multiple pods can be created on the fly through scalability features such as VMSS ... etc.
If you want Analytical capability on-prem you will use SQLServer 2019 BDC but if you want a Cloud based DWH with analytical capability features you will use Synapse
explain the difference between SQL Server 2019 BDC vs Azure Synapse Analytics
Server is OLTP and Synapse is OLAP. :D
other than OLAP & OLTP differences? Why would one use Analytics over SQL Server 2019 BDC?
Purely from a terminology point of view their product management have no clue what they are doing.
"SQL Server" is a DYI/on-prem/managed-by-you DB.
Fully Azure managed SaaS version of SQL Server is known as Azure SQL Database.
They also have "Azure SQL Managed Instance", and "SQL Server on Azure VM".
Azure Synapse is renamed Dedicated SQL-Pools.
Azure Synapse On-demand is renamed to Serverless SQL-Pools.
Azure Synapse Analytics = Dedicated + Serverless + bunch of ML services.
I'm going to answer assuming your question is:
Why would one use "Azure Synapse Dedicated or Serverless" over SQL Server?
SQL Server is on prem DIY, other is SaaS, fully managed by Azure. With this comes all the pros/cons of SaaS like No CAPEX, no management, elastic, very large scale, ...
Synapse' USP is it's MPP, which SQL Server does not have. Though I see things like Polybase and EXTERNAL TABLES being supported by SQL Server.
Due to MPP architecture, Synapse's transactional performance is worst by far (that I've seen). E.g. Executing INSERT INTO xxx VALUES(...) to add one row via JDBC would take about 1-2 seconds as against 10-12 seconds for importing CSV files with 10s of thousands of rows using COPY command. And INSERT INTO does not scale with JDBC batching. It'll take 100 seconds to insert 100 rows in one batch.
It is not your fault that you are confused. IMO Azure Product Management for Databases (SQL Server, DW, ADP, Synapse, Analytics and the 10 other flavors of all these) have no clue what they want to offer 2 years from today. Every product boasts of Big Data, Massive this and that, ML and Analytics, Elastic this and that. Go figure.
PS: Check out Snowflake if you haven't.
I'm not affiliated with Microsoft or Snowflake.
I believe the user user3129206 is asking
SQL Server 2019 BDC vs Azure Synapse Analytics
not
SQL Server vs Azure Synapse Analytics
so the first answer is relevant.
The only thing I'd argue is that the BDC is also an MPP like Synapse because of Pods in Kubernetes if implemented right, with many servers + HDS.
I plan to test BDC on-premises and see how demanding the install and maintenance are.
The neat thing about the BDC seems to be easy, partially or fully, to port it from on-premises to Azure or any cloud.
It seems that BDC is both OLTP and OLAP, trying to provide the best of both worlds.
As I am on the same comparison quest, I'll try to get back and share what I learn.
I'd like to host a Windows service application using e.g. Azure on AWS. I know I can modify my application to be an Azure worker role. Can I do the same thing with AWS or is there a better hosting provider. My application uses a database preferably SQL Server.
AWS is an IaaS - Infrastructure as a service, you can very much take a Windows Server 2008 R2 - EC2 instance and treat it as your own laptop or computer or server(just take RD) and deploy your windows service.
Regarding the DB, you can install SQL Server or MySql in the same instance (if you are fine with performance) or put the DB server in a separate EC2 instance. If you are worried about adding more EC2 instances, RDS is also an option available.
Since the AWS AMI (Amazon Machine Image) is a standard Windows 2008 operating system (various editions) you can create and deploy a Windows service as you normally would - and in the .NET world, Windows Service is still the way to go. Azure worker roles only work in Windows Azure.
With SQL Server on AWS you can use an AMI with SQL on already or install your own (see the pricing options for windows/SQL instances) but you will not have failover functionality as you can only have express or standard. To have redundant SQL servers you would need to do something like database mirroring or replication and keep it running yourself. There is no database service for SQL on AWS like there is with RDS (mySQL and Oracle) or SQL Azure