A Fine Slice Of SQL Server
In this video, we will take a look at two KPIs for measuring avidity. We will also show off how to use ranking window functions to order groups of customers.
Click through for the video. There are far too many measures of avidity for me to do a good job explaining them all, and so many of them are closely tied to the specific nature of the business, but hopefully this at least gives you ideas of how the business side may look at user avidity or stickiness.
Comments closedAnil Kumar Moka locks down a Snowflake instance:
In this practical guide, we’ll explore techniques to help you secure your use of Snowflake:
- Foundational Security Setup
- Secure Views and Their Critical Role
- Row-Level Security Implementation Methods
- Dynamic Data Masking Strategies
- Encryption and Data Protection
- Best Practices and Common Pitfalls
Read on for the full article.
Comments closedSebastiao Pereira creates a function:
It is very usual to have a set of discrete data points but sometimes it is necessary to estimate values between those points. Is it possible to create a function to do this in SQL Server?
It turns out that the answer is “yes.” Click through to see how.
Comments closedHaripriya Naidu explains SARGability:
Having the right index is helpful, but are you using the predicate (
WHEREclause) correctly to make efficient use of that index?This is where the term SARGable comes into play. SARGable stands for Search ARGumentable. If SQL Server is able to limit the search space while evaluating the predicates and can seek right at the page(s) to get the values, then it is SARGable.
Read on for an explanation of why this is important, as well as several examples of what is SARGable versus what isn’t. The most important thing about SARGability is that you pronounce it like “Sarge” and not “sarg.”
Comments closedGreg Low describes a common business problem:
But while food wholesale systems will need to deal with quantities like I described in that post, they often have another layer of complexity. Items are often sold by:
- Quantity
- Weight
- Quantity and Weight
This is an interesting look at how the domain can drive what a proper solution looks like. It also seems like a good use case for 6th normal form, with unit quantity and unit weight tables to prevent NULL from cropping up.
Comments closed