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.


Labels:

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         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more