Skip to main content

Azure SQL Learning Tools

Although every developer seems to know the latest and greatest new Javascript framework, some other more basic(/important?) skills seems to be lacking.

One of these skills is good knowledge of SQL (Server). Although ORM’s made our life as developers a lot easier it has the side effect that people don’t know how to write a SQL query anymore.

It is painful to watch how I see developers struggle when they have to write a stored procedure (a what…?). 

So for all these developers out there that recognize themselves in the story above, you are lucky. The Azure Data team created a lot of new content that will help both beginners being introduced to Azure as well as SQL experts learn how to understand the benefits of Azure SQL.

From the announcement:

Microsoft Learn learning path: This six-course Azure SQL fundamentals learning path provides a built-in lab environment for you to learn at your own pace without a subscription.

YouTube/Channel9 series: We offer more than 60 videos to help beginners learn more about Azure SQL. Viewers can experience on-demand training through Microsoft Developer and Azure SQL playlists on YouTube and Channel9.

GitHub content: Learners and educators can dig into open-source code in a scenario-driven GitHub workshop, where forking and redelivering is encouraged. You can access this content by visiting the SQL Server workshops page and selecting “Workshop: Azure SQL”.

Learn Live in the Azure SQL Bootcamp: In this four-day series of live sessions, Microsoft SQL experts Anna Hoffman and Bob Ward will help you get ramped up and support you as you learn. You can sign up for Azure SQL Bootcamp here to join us.


Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...