Gurvann 🔶 GUENNEGUES

Came across this tricky question while preparing for Databricks professional certification 🚀: 👉 Question: An external object storage container has been mounted to the location /mnt/finance_eda_bucket. The following logic was executed to create a database for the finance team: After the database was successfully created and permissions configured,a member of the finance team runs the following code: 𝗖𝗥𝗘𝗔𝗧𝗘 𝗗𝗔𝗧𝗔𝗕𝗔𝗦𝗘 𝗳𝗶𝗻𝗮𝗻𝗰𝗲_𝗲𝗱𝗮_𝗱𝗯 𝗟𝗢𝗖𝗔𝗧𝗜𝗢𝗡 '𝗺𝗻𝘁/𝗳𝗶𝗻𝗮𝗻𝗰𝗲_𝗲𝗱𝗮_𝗯𝘂𝗰𝗸𝗲𝘁'; 𝗚𝗥𝗔𝗡𝗧 𝗨𝗦𝗔𝗚𝗘 𝗢𝗡 𝗗𝗔𝗧𝗔𝗕𝗔𝗦𝗘 𝗳𝗶𝗻𝗮𝗻𝗰𝗲_𝗲𝗱𝗮_𝗱𝗯 𝗧𝗢 𝗳𝗶𝗻𝗮𝗻𝗰𝗲; 𝗚𝗥𝗔𝗡𝗧 𝗨𝗦𝗔𝗚𝗘 𝗢𝗡 𝗗𝗔𝗧𝗔𝗕𝗔𝗦𝗘 𝗳𝗶𝗻𝗮𝗻𝗰𝗲_𝗲𝗱𝗮_𝗱𝗯 𝗧𝗢 𝗳𝗶𝗻𝗮𝗻𝗰𝗲; ❓If all users on the finance team are members of the finance group, which statement describes how the tx_sales table will be created? 𝗖𝗥𝗘𝗔𝗧𝗘 𝗧𝗔𝗕𝗟𝗘 𝗳𝗶𝗻𝗮𝗻𝗰𝗲_𝗲𝗱𝗮_𝗱𝗯.𝘁𝘅_𝘀𝗮𝗹𝗲𝘀 𝗔𝗦 𝗦𝗘𝗟𝗘𝗖𝗧 *  𝗙𝗥𝗢𝗠 𝘀𝗮𝗹𝗲𝘀 𝗪𝗛𝗘𝗥𝗘 𝘀𝘁𝗮𝘁𝗲 = "𝗧𝗫"; A. A logical table will persist the query plan to the Hive Metastore in the Databricks control plane. B. An external table will be created in the storage container mounted to /mnt/finance_eda_bucket. C. A managed table will be created in the DBFS root storage container. D. An managed table will be created in the storage container mounted to /mnt/finance_eda_bucket. I thought the answer is external table mounted to /mnt/finance_eda_bucket but I was wrong. In Databricks, even if the database is mounted on an external location, a table is considered external only if it is explicitly created with a reference to an external location. If you create a table without specifying the location, Databricks will create a managed table, and the data will be stored in the default location of the metastore, regardless of the external location of the database. To create an external table, you must explicitly specify the external storage location while creating the table, like this: CREATE TABLE my_table (id INT, name STRING) LOCATION '/mnt/external-storage/data/'; 💡In this case, D is the right answer as the word LOCATION is not specified while creating table. Although the data will be stored in an external location but the table will still be a managed table 📝 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆𝘀: Managed Tables are convenient when you want Databricks to take care of both data and metadata. When you drop the table both metadata and data itself drop. External Tables give you flexibility by keeping data in external storage, which is ideal for scenarios where data location is crucial. Drop an External Delta table, only the table metadata is deleted. The actual data remains intact in the external storage layer (such as an Azure Data Lake Storage or an Amazon S3 bucket) where it was originally stored. Reference: https://lnkd.in/e-F9DaaN https://lnkd.in/eYJN6Fgr #databricks #databrickscertified #dataengineer

6

2 commentaires

🚀 [English Version] Discover the Secret to Connecting Your Azure Function to Cosmos DB Like a Pro! 🌐 Are you facing challenges configuring the Cosmos DB client in your Azure Functions? 🤔 Many development teams struggle to ensure their Cosmos DB integrations are secure, efficient, and scalable. In my latest article, "How to Configure the Cosmos DB Client Applying Clean Code Principles in an Azure Function with TypeScript," I provide a step-by-step guide that not only covers Cosmos DB configuration but also incorporates Clean Code principles for modular and clear design. 🔍✨ With practical examples on how to implement credential providers using Managed Identity and Service Principal, you'll gain a solid understanding of how to securely and efficiently connect your functions. Check out the article and learn how to optimize your data architecture using Azure Well-Architected and Cloud Adoption Framework best practices. 🛠️📈 👉 Read the article here: https://lnkd.in/dgizVsC5 Let’s transform the way we interact with Cosmos DB! 💡💻 #Azure #CosmosDB #CleanCode #AzureFunctions #Development #Tech #mvp #mvpbuzz #mvpbr

13

Watch Luigi Nardi's talk from #PosetteConf 2024 🌟 “Autotuning PostgreSQL on Azure Flexible Server” and Explore the world of #PostgreSQL parameter tuning & see a proof-of-concept for autotuning Azure Database for PostgreSQL Flexible Server 🌐

4

🔥🔥🔥 Shortcuts, Capacities and Costs : Some Considerations 🔥🔥🔥 Discover how shortcuts can affect the capacity consumption and all the possible architectures we can build from this feature Link in the comments #microsoftfabric #powerbi #dataplatform #lakehouse #capacities

4

1 commentaire

Today I am sharing one of the important feature update related to Microsoft Teams and Power Automate. New Feature : Microsoft Teams is introducing a ‘Workflow builder‘ feature. This feature allows us to describe the automation we need. It helps us get a matching workflow. Microsoft Teams – Future Update – Describe it to design it in Teams Workflows - https://lnkd.in/dxYikqwp In this article I am discussing this new feature in detail with demo. Useful article for Microsoft Teams administrators and Power Automate developers. HAPPY LEARNING 😊 HAPPY SHARING 😊 #microsoft365 #m365 #microsoft365dev #office365 #o365 #sharepoint #sharepointonline #powerautomate #microsoftteams #teams #powerplatform #workflows

7

🔥🔥 Microsoft Fabric : Azure SQL Mirroring and CDC - How to Choose 🔥🔥 This time we have a presentation for starters and a presentation for experts - in the same day Come enjoy the networking and technical knowledge Register now on the link in the comments !

3

2 commentaires

😍 Amazing article on Power Platform Dataflow! An ETL completely integrated into the Power Platform ! Which will really allow you to carry out powerful data integrations, in particular thanks to the library of pre-existing connectors available but above all thanks to the possibility of using Power Query! This article is a real mine of information if you want to explore the possibilities of #Dataflow, a tool that is certainly still little known. A BIG thank you to our author Stéphane Pelhatre for this nice deep dive! #elca #dynamicschronicles #microsoft #powerplatform #dataverse #etl #data #powerapps #powerquery #powerbi #azure https://lnkd.in/eXzNQ7Ee

49

7 commentaires

#Copilot can now act on multiple files in OneDrive and SharePoint. Let's discover what it can do and what the limitations are. https://lnkd.in/eawidGFQ

13

2 commentaires

Talend 8.0.1 now supports JWT token validation – a long awaited feature for REST services security! Talend developers can now seamlessly integrate with modern identity providers like Azure Entra ID or Keycloak, moving away from legacy security practices. My blog post covers the benefits of using JWT tokens and how to get started. https://lnkd.in/ere7W2FJ

2

Rien de moins que 63 nouveaux rapports Power BI pour Dynamics 365 Business Central!" dans le 2024 Wave II release. 😎 Nothing less than 63 new Power BI reports for Dynamics 365 Business Central in the 2024 Wave II release! 😎 https://lnkd.in/eTD24fDA #PowerBI #MsDyn365BC

20

Excited to announce a new collaboration between #AzureAISearch and #LlamaIndex 📢 : ✅ Take a look into this post, as we teach you how to use LlamaIndex in pre-retrieval for query transformations and use Azure AI Search for advanced retrieval techniques: https://lnkd.in/gQDMPrpb

14

SQL server and editions: which one to choose? Do you really need entreprise edition for your MSSQL server and pay 4 times more? Do you really need that much CPU? Do you actually know what your databases are actually consuming in ressources and what contentions it does have? CPU, RAM, IOs, Logical? There are a lot of misconception that if you are serious and a company, you need entreprise edition. Well it depends on many things: - Hardware limitation and actual usage - HADR and RPO/RTO objectives - Data usage pattern and data lifecycle on your large tables - Intelligent query processing algorythm - Saas, multi-tenancy and sharding strategy You might be totally fine on Standard edition! Do not hesitate to contact me if you are wondering (provide 30-mn call for free). As an example, I have a client running billions of writes per day on a 30 TB database stack that I downgraded from Entreprise to standard edition and optimize their databases. Not only everything is faster but they saved a considerable amount on licencing cost without compromising on high availability. #sqlserver #cpu #EntrepriseVsStandard

16

10 commentaires

Generally Available: Support for .NET 8 using the in-process model in Azure Functions

1