what is the difference between cloud adoption and cloud migration?
As far as I'm concerned cloud adoption is utilizing different services from csp where as cloud migration is migrating from on-premise to cloud. But some scholars consider it as a the same concept.
Related
We are implementing SAP analytics cloud and like to know if there are premade reports and tools or even ideas to build useful reports that connects to our S/4HANA system.
What is the best method to sync medical images between my client PCs and my Azure Blob storage through a cloud-based web application? I tried to use MS Azure Blob SDK v18, but it is not that fast. I'm looking for something like dropbox, fast, resumable and efficient parallel uploading.
Solution 1:
AzCopy is a command-line tool for copying data to or from Azure Blob storage, Azure Files, and Azure Table storage, by using simple commands. The commands are designed for optimal performance. Using AzCopy, you can either copy data between a file system and a storage account, or between storage accounts. AzCopy may be used to copy data from local (on-premises) data to a storage account.
And also You can create a scheduled task or cron job that runs an AzCopy command script. The script identifies and uploads new on-premises data to cloud storage at a specific time interval.
Fore more details refer this document
Solution 2:
Azure Data Factory is a fully managed, cloud-based, data-integration ETL service that automates the movement and transformation of data.
By using Azure Data Factory, you can create data-driven workflows to move data between on-premises and cloud data stores. And you can process and transform data with Data Flows. ADF also supports external compute engines for hand-coded transformations by using compute services such as Azure HDInsight, Azure Databricks, and the SQL Server Integration Services (SSIS) integration runtime.
Create an Azure Data Factory pipeline to transfer files between an on-premises machine and Azure Blob Storage.
For more details refer this thread
Why does external I.P. need access to on-prem sql database when copying data with ADF to Azure SQL?
It looks like on-prem sql makes a direct connection to Azure SQL (bypassing ADF). Is this by design or do I follow the wrong workflow?
Data Factory use the integration runtime to help us create the connection to the Source/Sink dataset. Azure integration runtime for cloud dataset and Self-host integration runtime for on-premise source/sink dataset.
The integration runtime (IR) is the compute infrastructure that Azure
Data Factory uses to provide data-integration capabilities across
different network environments. For details about IR, see Integration
runtime overview.
A self-hosted integration runtime can run copy activities between a
cloud data store and a data store in a private network. It also can
dispatch transform activities against compute resources in an
on-premises network or an Azure virtual network. The installation of
a self-hosted integration runtime needs an on-premises machine or a
virtual machine inside a private network.
Azure integration runtime is provides by ADF in default. The self-host integration runtime must be created manually.
That means Data Factory can not access the on-prem SQL database directly. It need the self-host integration runtime to help us connect to the on-prem SQL database.
It means that the on-prem sql does not make a direct connection to Azure SQL(bypassing ADF. That why external I.P. need access to on-prem sql database when copying data with ADF to Azure SQL.
HTH.
What are the differences between the following Azure Services?
Azure Synapse Analytics (formerly SQL DW)
Azure Synapse Analytics (private link hubs preview)
Azure Synapse Analytics (workspaces preview)
Are these three different products? Or are the two preview services just new features that will eventually be added into Azure Synapse Analytics?
The documentation is a little confusing. This FAQ (https://learn.microsoft.com/en-us/azure/synapse-analytics/overview-what-is) for the workspaces preview, for example, just looks like a FAQ for the overall Azure Synapse Analytics service.
It would be useful to link to a document mentioning these terms so I could have some context. Without context, this is my understanding of these:
Azure Synapse Analytics (formerly SQL DW)
This is just the MPP relational platform piece of "Azure Synapse Analytics"
You can connect to it using Azure Data Studio, SQL Server Management Studio, or Synapse Workspace and run SQL queries on it. It's a relational database that stores data across 60 shared-nothing nodes
Azure Synapse Analytics (private link hubs preview)
private link is a new feature across many Azure resources (data lake etc.) that allows you to confine connectivity to internal Azure VNets, meaning that you can use the resource without requiring public access. This feature is not specific to Synapse, it's a network connectivity feature being rolled across multiple azure components
Azure Synapse Analytics (workspaces preview)
This is the actual front end that has tabs for various analytics components. One component is the MPP platform that used to be called SQL DW. Another component is MS spark engine. Other components are Power BI and Data Factory.
Do you have a use case or an objective here?
I have hard time with Azure Functions on Azure Government. I need to create a C# trigger bases process on Azure Storage. The goal is to automate the process of the loading the files into Azure SQL DB when a file is dropped into Azure Storage.
Since Azure Functions in Azure Government are not fully comparable to Azure Function in regular Azure and not all UIs are the same, I can't deploy the function to trigger on a storage file.
I was able to build the process in regular Azure Cloud following instructions from https://github.com/yorek/AzureFunctionUploadToSQL but since Azure Government is missing the UI for Azure Functions I'm having hard time to replicating the process in Azure Government.
Portal UI support is not yet available in Azure Government, but it is coming soon. Additionally, Azure Government currently supports "App Service plan" ("Consumption plan" coming soon).
In the meantime, you can do everything you need. First, provision your Azure Function in Azure Gov via the Azure CLI by following this Quickstart example for Functions on Azure Gov. That same link also shows you how you can use Visual Studio to set up your triggers (in your case, a Blob trigger).
Once complete, deploy your Function to Azure Gov with Visual Studio.