A Fine Slice Of SQL Server
Connie Xu makes an announcement:
We’re thrilled to announce that the Copy job Activity is now in Preview!
This new orchestration activity brings the simplicity of the Copy job item directly into your Microsoft Fabric Data Factory pipelines, enabling you to manage data movement alongside transformations, notifications, and more; all in one place.
Read on to learn more about it, including how it differs from the Copy activity and the Copy job item.
Leave a CommentJon Vöge sends along some data:
A common misconception about Translytical Task Flows is that the only way for you to parameterize and pass user inputs to the User Data Function, is through Slicers in Power BI.
That is not true at all.
In fact, one of the most powerful ways of integrating Task Flows into your Power BI reports, is by allowing user selections made in visualisations in your report, flow through to your task flow.
Read on to see how you can do this.
Leave a CommentBoniface Muchendu wants to avoid DAX for this calculation:
Power BI visual calculations provide a simplified way to perform time-based comparisons like week-over-week (WoW) analysis without writing complex DAX. Power BI’s time intelligence functions are powerful, but they can become challenging when working with custom calendars or unique business logic. If you’ve ever struggled with calculating WoW performance, this post will show you how to streamline the process using visual calculations.
Read on to see how. Though one thing to keep in mind is that it says week-over-week, but that assumes you have data for each week. I don’t believe this solution would cleanly handle gaps in data, so that would be something you’d want to do beforehand.
Leave a CommentAndy Brownsword takes a closer look at the big three join operators in SQL Server:
In the previous post I explained Join Operators in SQL Server. Whilst compiling that I dug a little deeper and came across a few interesting points I thought were worth sharing.
Let’s look at behaviour of the operators which may occur under specific conditions. Hopefully you find them as interesting as I did:
Click through for an interesting tidbit about nested loops joins, merge joins, and hash joins.
Leave a CommentAnshika Varshney takes us through some secrets management:
Secret management is a critical part of working with Kubernetes. When working with Kubernetes, you’ll often need to store and use sensitive information — like database passwords, API keys, and certificates. That’s where Kubernetes Secrets come in. But here’s the thing: while Kubernetes provides a way to store secrets, using them incorrectly can still expose your sensitive data.
This blog will walk you through:
- What Kubernetes Secrets are
- How they work
- Common mistakes (the wrong way)
- Best practices (the right way)
- Real-life examples and configurations
Read on for the full article. I do want to iterate what I consider the most important of Anshika’s points: these things should never go into source control. The problem is, source control history is a lot more permanent than people customarily think about, so if you accidentally checked in a password in a config file somewhere, then got rid of the line with the password in it, a bad person with access to your source control can still look at history and find that password. The mechanism to rewrite Git history to remove a line’s existence is purposefully difficult, so a lot of developers don’t even know that it’s possible. But even then, if you’re hosting on someplace like GitHub and forks are enabled, rewriting history in your fork doesn’t rewrite it in somebody else’s fork, so again, a bad person with a fork from the right time frame could still see your exposed password.
The only fix is to cycle credentials if you ever do accidentally expose a password or key in source control files.
Comments closedPriya Sathy has an announcement:
The first release candidate (RC0) of SQL Server 2025 is now available. As we move toward general availability, our focus shifts to delivering enhanced stability, performance, and product improvements based on your feedback.
There are a few new features that Priya specifies in the post, so check those out. This also puts us on track for a GA delivery right around conference season.
Comments closedNicky van Vroenhoven has a public service announcement:
Microsoft Fabric is changing how service principal access to public APIs is controlled. The existing all-or-nothing tenant setting was split into two separate settings — giving us admins more granular control, but also introducing a change you might need to act on after August 1, 2025.
Click through to see how you might have been able to learn this, as well as the consequences of this change.
Comments closedErik looks at a classic performance difference between ROWS and RANGE, as well as what batch mode does to even the score. This is particularly nice because ROWS and RANGE both have their utility and focusing on one versus the other for performance differences can lead to awkward development practices to get around a window spool.
Erik also focuses primarily on batch mode on rowstore, so keep in mind the minimum requirements for it: 131,072 (or 2^17) rows in at least one table in the query, at least one operator that benefits from batch mode (which we’d cover in the window function), at least one input of the batch with 2^17 rows, and where the batch mode cost is lower than the row mode cost.
Comments closedChris Webb highlights some community efforts:
There are a lot of really cool free, community-developed tools and resources out there for Power BI and Fabric – so many that it’s easy to miss announcements about them. In this post I thought I’d highlight a few that came out recently and which you might want to check out.
Click through for several good resources, and there are a couple of additional ones in the comments as well.
Comments closedRandolph West has a script for us:
Part of my job at work is to update Transact-SQL reference content. System dynamic management views (DMVs) have permissions that are managed in the SQL Server Database Engine source code, so it’s a little tricky to figure out the required permissions for a specific DMV.
This blog post provides a stored procedure that uses
sys.fn_builtin_permissionsto calculate permissions, but keep in mind that any custom permissions that you’ve implemented, can override the defaults.
This can serve as a quick check for whether your user account has the necessary permissions to access DMVs in a particular database.
Comments closed