Skip to main content

From DBA to Data Engineer in Azure

I recently moved a role

From being a DBA Manager, Who is responsible for the operational databases.

I moved to manage the data engineering group.

So what exactly is the difference between the two functions?


DBA - Production Databases:

  • SQL\ NoSQL- 24*7, powerful server on premise or on the cloud, managed or semi managed, security tasks, high performance is a target, multiregional, HA as top priority.

  • Developers are using Microservices - so we have many applications many services and many many Databases.

  • Many kinds of DB's like Cloud IAAS and PAAS.

  • Secure and audit the data is must.

  • The Clusters must have Uptime as long as we can achive.

  • Data Modeling - is so important too.


Challenges and Problems in the data bases systems

  1. Lots of DB’s

  2. Lots of creators / no standards

  3. Lots of Consumers (Query, tools, SLA)

  4. Raw data

  5. Lots of data resources

  6. Data silos

In Data Engineering we have other challenges for example we have Data lake and Data Warehouses :

  1. Batch process.

  2. Stream Process.

  3. many data sources

  4. ETL and EL.

  5. Data Quality \ Governance \ Catalog.

  6. New skill sets

  7. Lots of consumers with difference skill sets.


It is a new and fascinating world, with special challenges and its importance is increasing day by day in organizations.


If once only analysts or data scientists consumed information from the Data Lake, today the apps are already taking information from there.


If once it was enough to know SQL to access the information - today you need to know much more and on the other hand the role of the data engineer to make the information accessible to those who need it in the simplest and easiest way.


The interesting challenges will be presented in the following posts.

stay tuned

Labels:

Comments

Post a Comment

Popular posts from this blog

How to restore deleted Azure Synapse dedicated SQL pool

  Existing dedicated pool can be easily restored from Azure portal or PowerShell command, but for now deleted pool could be restored from PowerShell only! Example: # Connect to Azure with system-assigned managed identity $AzureContext = (Connect-AzAccount -Identity).context # set and store context $AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext # $AzureContext = Set-AzContext -SubscriptionName $SubscriptionName -DefaultProfile $AzureContext $SubscriptionName="Databases" $ResourceGroupName="stg-rg-we" $ServerName="stg-synapse-we"   $DatabaseName="sql_we_2023_11_07_13_42" $NewDatabaseName="sql_dp_we_deleted" ######################################## $token = (Get-AzAccessToken -ResourceUrl https://database.windows.net).Token $SubscriptionId = "ce088f9e-1111111a3914b" $DedicatedPoolEndPoint = "stg-synapse-we.sql.azuresynapse.net" $DedicatedPoolName = $DatabaseNam...
Post a Comment
Read more

The journey to the Lakehouse

A long time has passed since the last post, we have gone through a long and tedious journey to adapt what Azure offers us, to our needs. Our needs were simple, the Current Datawarehouse (SQL Server on VM inazure) served the BI. ML teams worked on GCP, we want to let both teams to work on Azure in a platform that will have the ability to scale and will not fail every 2 days. We checked: Snowflake on azure Synapse analytics GCP We decided to go for the full Azure product for the reasons: Migration time support costs Synapse as a platform contains many components, and the challenge was to find what fits  us as an organization and as a group. The knowledge of the people and their abilities influenced the plans. Here's what we planned and what we did: We start to put everything in the Data Lake in parquet or delta format, build on top of Azure ADLS gen 2. We had to move some data to T-SQL compatible platform, so this involves setting up a dedicated Synapse pool , which is a fully man...
Post a Comment
Read more

Configuring secondary database in Azure SQL DB - Bug found

Hi All Last week we had an issue with a secondary DB in geo replication and fail over group. To make the long story short we had to delete the secondary and recreate a secondary from scratch . And now let me tell you the story, we build a DB in P6 tier - very high, expensive and highly available. Then we add a geo replication copy via the platform, like it shows here. This is take from MSFT documentation: https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview It is written:  " Both primary and secondary databases are required to have the same service tier. It is also strongly recommended that the secondary database is created with the same backup storage redundancy and compute size (DTUs or vCores) as the primary. If the primary database is experiencing a heavy write workload, a secondary with lower compute size may not be able to keep up with it. That will cause redo lag on the secondary, and potential unavailability of the secondary. To mit...
Post a Comment
Read more