A Fine Slice Of SQL Server
Vlad Drumea is not a fan of sequences:
This is a script that I wrote to help me next time I might need to bulk reseed out-of-sync SQL Server sequences tied to default constraints.
Click through for a demo of the problem, as well as Vlad’s script to fix it.
Leave a CommentDaniel Janik notes the cyclical nature of things:
For years, the narrative pushed was that traditional relational databases were ill-suited for the scale and complexity of modern BI solutions. The marketing was something like: “Databases don’t belong in BI; use Spark!” We embraced distributed computing frameworks, data lakes, and complex ETL pipelines to move data from operational databases into analytical engines. The idea was to separate transactional workloads from analytical ones to ensure performance and scalability. Spark, with its ability to handle massive datasets and flexible processing, became the darling of the data world.
“Remember, Sully, when I said you don’t need databases anymore?”
“Yeah, Matrix, I remember!”
“I lied.”
Leave a CommentTeo Lachev gives us a case study:
I’ve recently written about strategies for addressing memory pressures with Fabric large semantic models and I mentioned that one of them was switching to Direct Lake. This blog captures my experience of migrating a real-life import semantic model to Direct Lake.
Read on for Teo’s notes and tips.
Leave a CommentErik mentions that he doesn’t often see GROUPING SETS in the wild. I’ve used them several times. And the use of the term “several times” probably gives you exactly the feeling that I intended. I really like grouping sets for very specific analytical system purposes (at least for moderate-sized datasets), so I’m glad that syntax is there. But outside of reporting queries, it’s a really uncommon bit of syntax.
Chad Callihan is overdrawn at the memory bank:
When you specify the max amount of memory that SQL Server can use, you may think that’s all the memory to be used for the buffer pool. That’s not the case. SQL Server will use memory not only for the buffer pool but also in tasks such as sorts, memory grants, and other internal tasks. These tasks can swoop in and “steal” memory from the buffer pool, causing more work for SQL Server.
Click through for some notes on the topic, as well as your reminder that “128 GB for the buffer pool” in Standard Edition doesn’t mean “128 GB total memory usage for SQL Server.”
Leave a CommentAndy Brownsword breaks things up:
Sometimes you want to segment records. It may be splitting a customer base for marketing purposes, or segmenting a user base for a new feature. Good segmentation makes clean divisions in the data.
In this post we’ll see a way to achieve that with a great deal of help from Window Functions.
Click through for Andy’s motivation, which is a way that absolutely will not work the way you want it to.
Leave a Comment